False Positive | crm.cut2code.com

[ambiscale-developers]

What are the subjects of the false-positive (domains, URLs, or IPs)?

crm.cut2code.com

Why do you believe this is a false-positive?

I believe this is a false-positive because it's one of our internal tool. I'm note sure if it's in your database, as we are not able to download the list from your server. I found this on VirusTotal: https://www.virustotal.com/gui/domain/crm.cut2code.com/detection

Please, remove our legitimate domain from your lists.

Best!

How did you discover this false-positive(s)?

VirusTotal

Where did you find this false-positive if not listed above?

I discovered this false-positive by...
n/a

Have you requested a review from other sources?

I have requested a review from...
n/a

Do you have a screenshot?

Screenshot

na/

Additional Information or Context

I have also noticed that...
n/a

[phishing-database-bot]

Verification Required

@ambiscale-developers, thank you for submitting a false positive report! To help us verify your ownership of the affected domain(s), please complete the following steps:

1. Set a DNS TXT record for the domain(s) listed in this issue with the following details:

   • Record Name: _phishingdb
   • Record Value: antiphish-27beec43d77f5d0dd586313c840b9f5ac26fb8ff

   Your Verification ID: antiphish-27beec43d77f5d0dd586313c840b9f5ac26fb8ff

2. Wait for DNS propagation (this may take a few minutes to a few hours).

3. Reply to this issue once the TXT record has been set.

Important Notes

• Verification does not guarantee whitelisting. The Phishing.Database team will review your report after verifying ownership, but the decision to whitelist depends on further investigation and analysis.
• If the record cannot be set or you need alternative methods of verification, please contact us at [email protected] - preferably from the domain's official email address.

How to Check the TXT Record ?

You can verify that the TXT record is properly set using:

• Online tools like MXToolBox TXT Lookup.
• The command line:

  dig TXT _phishingdb.example.com
  

Thank you for your cooperation! We will address your issue as soon as possible after verification.

The Phishing.Database Project Team.

[ambiscale-developers]

`$ dig TXT _phishingdb.crm.cut2code.com

; <<>> DiG 9.10.6 <<>> TXT _phishingdb.crm.cut2code.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39070
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;_phishingdb.crm.cut2code.com. IN TXT

;; ANSWER SECTION:
_phishingdb.crm.cut2code.com. 300 IN TXT "antiphish-27beec43d77f5d0dd586313c840b9f5ac26fb8ff"

;; Query time: 75 msec
;; SERVER: 100.80.255.254#53(100.80.255.254)
;; WHEN: Tue May 06 17:02:55 CEST 2025
;; MSG SIZE rcvd: 148
`

MXToolBox: https://mxtoolbox.com/SuperTool.aspx?action=txt%3a_phishingdb.crm.cut2code.com&run=toolpage