Registrar abuse contact
The address the registrar publishes for abuse reports about this domain.
Every ICANN-accredited registrar must publish an address where anyone can report abuse of the domains it manages: phishing, malware, spam, fraud. SiteScan takes that address from the registrar's abuse contact in the RDAP record.
Why it matters to the owner
- Complaints about your domain go here. If your site is hacked and starts serving phishing pages or malware, reports reach the registrar through this address. A registrar that gets no reply from you may put the name on
clientHold, which removes it from DNS. Make sure the registrar can reach you quickly, through contact data that is current. - Reporting other domains. When a lookalike domain imitates your brand or a phishing site targets your customers, this is the address to write to about that domain. A good report names the exact URLs, says what they do, includes evidence and the date you saw them.
What the row shows
The row is informational and appears when the registry record carries an abuse address. It is the registrar's address, not yours; it says nothing about your own security contact. To give researchers a direct way to report vulnerabilities in your site, publish security.txt. If the domain does end up on hold, the registry status row will show it.
See this check on your own site
Run a free scan: the report shows this row for your domain along with the other checks of the site audit.
More in “Domain registration”
What SiteScan checks
TLS certificate
- TLS certificate expiry
- Outdated TLS versions (TLS 1.0/1.1)
- TLS certificate chain
- TLS certificate issuer
- Certificate signature algorithm
Domain registration
- Domain registration expiry
- Registered domain name
- Domain registrar
- Domain registration date
- Domain last updated date
- Domain status codes (EPP)
- Domain transfer lock
- Registrar abuse contact
- RDAP and WHOIS data source
Indexing
- robots.txt file
- CSS and JS blocked in robots.txt
- XML sitemap
- Sitemap index file
- Off-domain URLs in the sitemap
- Sitemap lastmod dates
- Broken URLs in the sitemap
- RSS and Atom feed
Addresses & redirects
Security headers
- HTTP security headers and grade
- Strict-Transport-Security (HSTS) header
- Content-Security-Policy (CSP) header
- X-Content-Type-Options: nosniff
- X-Frame-Options and clickjacking
- Referrer-Policy header
- Permissions-Policy header
- HSTS preload list
- CORS and cross-origin reads
- HTTP TRACE method
Delivery & reputation
- Cache-Control header for HTML
- ETag and Last-Modified revalidation
- HTTP/3 and QUIC support
- Server version disclosure in headers
- DNS blocklist (DNSBL) check
Internal links
Exposure
- Exposed sensitive files (.env, .git, backups)
- Directory listing enabled
- Public JavaScript source maps
- Exposed WordPress endpoints
Well-known files
- security.txt file
- llms.txt for AI assistants
- llms-full.txt file
- ads.txt authorized sellers file
- humans.txt file
- Well-known change-password URL
DNS & email
- MX records (mail servers)
- SPF record
- DMARC record and policy
- DNSSEC signing
- CAA record
- Nameserver redundancy
- IPv6 support (AAAA record)
- MTA-STS policy
- TLS-RPT reporting record
- BIMI record (brand logo in email)
- Wildcard DNS record
- Dangling CNAME and subdomain takeover
Privacy & consent
- Analytics and tracking scripts
- Cookie consent banner
- Privacy policy link
- Terms of service link
- Imprint (Impressum)
- Accessibility statement
Core Web Vitals
- Lighthouse performance score
- Largest Contentful Paint (LCP)
- Cumulative Layout Shift (CLS)
- Interaction to Next Paint (INP)
- CrUX field data vs lab data