Identity
71
F
publicnode.com
Posture Score: 54/100
Scanned May 29, 2026 at 3:59 AM UTC
Score History
Attack Surface
0
Reputation
92
Identity Findings
Weak DKIM RSA key (~1296 bits) for selector 'mail'
RSA keys shorter than 2048 bits are considered weak. Current key is approximately 1296 bits.
💡 Generate a new 2048-bit (or larger) RSA key pair and update the DKIM record.
TLS certificate hostname mismatch on mx.publicnode.com
Certificate subject 'mx.theabyss.com' does not match hostname 'mx.publicnode.com'. SANs: mx.theabyss.com
💡 Obtain a TLS certificate that matches the mail server hostname.
No MTA-STS record found
Without MTA-STS, mail transport encryption cannot be enforced and is vulnerable to downgrade attacks.
💡 Publish a _mta-sts TXT record and host a policy file at https://mta-sts.publicnode.com/.well-known/mta-sts.txt
STARTTLS without MTA-STS or DANE protection
STARTTLS alone is vulnerable to downgrade attacks. Neither MTA-STS nor DANE is configured to enforce encryption.
💡 Deploy MTA-STS and/or DANE to protect against STARTTLS stripping attacks.
No CAA records found
No CAA records are configured. Any certificate authority can issue certificates for this domain.
💡 Add CAA records to restrict certificate issuance. Example: 0 issue "letsencrypt.org"
No TLS-RPT record found
Without TLS-RPT, you will not receive reports about TLS negotiation failures.
💡 Publish a _smtp._tls TXT record (e.g. "v=TLSRPTv1; rua=mailto:tls-reports@publicnode.com").
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup limits.
SPF record length OK (11 bytes)
SPF record is within safe DNS packet size limits.
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
DKIM key strength indicates modern key management
All DKIM keys use RSA-2048+ or Ed25519, consistent with current best practices.
No external DMARC report destinations
All DMARC report URIs point to the same domain — no external authorization needed.
Subdomains protected (sp=quarantine)
DMARC subdomain policy enforces quarantine or reject on unauthenticated subdomain mail.
MX records are valid
All MX records are properly configured.
ARC support likely available
MX server software appears to support ARC headers for authentication preservation.
Meets bulk sender authentication requirements
Domain has SPF, DKIM, and DMARC — meeting Google/Yahoo 2024 bulk sender requirements for email authentication.
SMTP security checks passed
No open relay, VRFY/EXPN, or banner disclosure issues detected.
SMTP RFC 5321 compliance checks passed
The mail server accepts postmaster@ and abuse@ and uses a valid FQDN in EHLO.
IPv6 readiness is good
IPv6 records are present and properly configured.
NS delegation is properly configured
All nameservers are responsive, consistent, and properly secured.
DNS responses are consistent across all nameservers
All authoritative nameservers return consistent answers with proper AA flags.
DNS TTL values follow best practices
All critical DNS record TTLs are within recommended ranges.
DKIM2 not detected
No DKIM key record with v=2 was found across common selectors. DKIM2 is an emerging standard and not yet widely deployed.
DMARC alignment: adkim=r, aspf=r
DKIM alignment is relaxed, SPF alignment is relaxed.
DMARCbis np tag absent
The DMARC record does not include the np (non-existent subdomain policy) tag. Consider adding np=reject to protect non-existent subdomains under DMARCbis.
Deprecated DMARCbis tags found: pct
The DMARC record contains tags deprecated in DMARCbis: pct. Consider removing these for forward compatibility.
DMARCbis psd tag absent
The DMARC record does not include the psd (public suffix domain) indicator. Consider adding psd=n to explicitly identify this as an organizational domain.
REQUIRETLS not advertised
The primary MX does not advertise REQUIRETLS (RFC 8689). This is an emerging standard — MTA-STS and DANE provide adequate TLS enforcement for most deployments.
No DANE/TLSA records found
DANE is not configured for any MX server. This is optional but provides strong certificate binding.
No BIMI record found
BIMI is not configured. Your brand logo will not display in supporting email clients.
Open mail ports on mx.publicnode.com
Detected open mail-related ports: 25
RFC 8058 one-click unsubscribe assessment
DKIM signing is configured. RFC 8058 compliance depends on List-Unsubscribe and List-Unsubscribe-Post headers being included in outbound messages and DKIM signatures.
MX IP network diversity
All MX IPs are in the same /16 network. Consider diversifying across networks for resilience.
SOA record parameters
Serial: 2405400321, Refresh: 10000s, Retry: 2400s, Expire: 604800s, Min TTL: 300s
Attack Surface Findings
Domain enumerability: high
The domain is highly enumerable. Zone transfers, NSEC zone walking, or a combination of factors make it easy to discover all DNS records.
💡 Restrict zone transfers, use NSEC3 instead of NSEC, consider wildcard certificates to reduce CT log exposure, and implement rate limiting on DNS queries.
Non-responsive IP for www.publicnode.com: 2606:4700:10::ac42:96a2
The subdomain www.publicnode.com resolves to 2606:4700:10::ac42:96a2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::ac42:96a2 is operational or remove the DNS record for www.publicnode.com.
Non-responsive IP for www.publicnode.com: 2606:4700:10::6814:1875
The subdomain www.publicnode.com resolves to 2606:4700:10::6814:1875 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::6814:1875 is operational or remove the DNS record for www.publicnode.com.
Non-responsive IP for ftp.publicnode.com: 2606:4700:10::6814:1875
The subdomain ftp.publicnode.com resolves to 2606:4700:10::6814:1875 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::6814:1875 is operational or remove the DNS record for ftp.publicnode.com.
Non-responsive IP for ftp.publicnode.com: 2606:4700:10::ac42:96a2
The subdomain ftp.publicnode.com resolves to 2606:4700:10::ac42:96a2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::ac42:96a2 is operational or remove the DNS record for ftp.publicnode.com.
Non-responsive IP for ns1.publicnode.com: 2606:4700:10::ac42:96a2
The subdomain ns1.publicnode.com resolves to 2606:4700:10::ac42:96a2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::ac42:96a2 is operational or remove the DNS record for ns1.publicnode.com.
Non-responsive IP for ns1.publicnode.com: 2606:4700:10::6814:1875
The subdomain ns1.publicnode.com resolves to 2606:4700:10::6814:1875 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::6814:1875 is operational or remove the DNS record for ns1.publicnode.com.
Non-responsive IP for ns2.publicnode.com: 2606:4700:10::6814:1875
The subdomain ns2.publicnode.com resolves to 2606:4700:10::6814:1875 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::6814:1875 is operational or remove the DNS record for ns2.publicnode.com.
Non-responsive IP for ns2.publicnode.com: 2606:4700:10::ac42:96a2
The subdomain ns2.publicnode.com resolves to 2606:4700:10::ac42:96a2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::ac42:96a2 is operational or remove the DNS record for ns2.publicnode.com.
Non-responsive IP for vpn.publicnode.com: 2606:4700:10::6814:1875
The subdomain vpn.publicnode.com resolves to 2606:4700:10::6814:1875 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::6814:1875 is operational or remove the DNS record for vpn.publicnode.com.
Non-responsive IP for vpn.publicnode.com: 2606:4700:10::ac42:96a2
The subdomain vpn.publicnode.com resolves to 2606:4700:10::ac42:96a2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::ac42:96a2 is operational or remove the DNS record for vpn.publicnode.com.
Non-responsive IP for remote.publicnode.com: 2606:4700:10::ac42:96a2
The subdomain remote.publicnode.com resolves to 2606:4700:10::ac42:96a2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::ac42:96a2 is operational or remove the DNS record for remote.publicnode.com.
Non-responsive IP for remote.publicnode.com: 2606:4700:10::6814:1875
The subdomain remote.publicnode.com resolves to 2606:4700:10::6814:1875 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::6814:1875 is operational or remove the DNS record for remote.publicnode.com.
Non-responsive IP for admin.publicnode.com: 2606:4700:10::ac42:96a2
The subdomain admin.publicnode.com resolves to 2606:4700:10::ac42:96a2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::ac42:96a2 is operational or remove the DNS record for admin.publicnode.com.
Non-responsive IP for admin.publicnode.com: 2606:4700:10::6814:1875
The subdomain admin.publicnode.com resolves to 2606:4700:10::6814:1875 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::6814:1875 is operational or remove the DNS record for admin.publicnode.com.
Non-responsive IP for portal.publicnode.com: 2606:4700:10::6814:1875
The subdomain portal.publicnode.com resolves to 2606:4700:10::6814:1875 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::6814:1875 is operational or remove the DNS record for portal.publicnode.com.
Non-responsive IP for portal.publicnode.com: 2606:4700:10::ac42:96a2
The subdomain portal.publicnode.com resolves to 2606:4700:10::ac42:96a2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::ac42:96a2 is operational or remove the DNS record for portal.publicnode.com.
Non-responsive IP for dev.publicnode.com: 2606:4700:10::ac42:96a2
The subdomain dev.publicnode.com resolves to 2606:4700:10::ac42:96a2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::ac42:96a2 is operational or remove the DNS record for dev.publicnode.com.
Non-responsive IP for dev.publicnode.com: 2606:4700:10::6814:1875
The subdomain dev.publicnode.com resolves to 2606:4700:10::6814:1875 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::6814:1875 is operational or remove the DNS record for dev.publicnode.com.
Non-responsive IP for staging.publicnode.com: 2606:4700:10::6814:1875
The subdomain staging.publicnode.com resolves to 2606:4700:10::6814:1875 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::6814:1875 is operational or remove the DNS record for staging.publicnode.com.
Non-responsive IP for staging.publicnode.com: 2606:4700:10::ac42:96a2
The subdomain staging.publicnode.com resolves to 2606:4700:10::ac42:96a2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::ac42:96a2 is operational or remove the DNS record for staging.publicnode.com.
Non-responsive IP for test.publicnode.com: 2606:4700:10::ac42:96a2
The subdomain test.publicnode.com resolves to 2606:4700:10::ac42:96a2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::ac42:96a2 is operational or remove the DNS record for test.publicnode.com.
Non-responsive IP for test.publicnode.com: 2606:4700:10::6814:1875
The subdomain test.publicnode.com resolves to 2606:4700:10::6814:1875 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::6814:1875 is operational or remove the DNS record for test.publicnode.com.
Non-responsive IP for api.publicnode.com: 2606:4700:10::ac42:96a2
The subdomain api.publicnode.com resolves to 2606:4700:10::ac42:96a2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::ac42:96a2 is operational or remove the DNS record for api.publicnode.com.
Non-responsive IP for api.publicnode.com: 2606:4700:10::6814:1875
The subdomain api.publicnode.com resolves to 2606:4700:10::6814:1875 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::6814:1875 is operational or remove the DNS record for api.publicnode.com.
Non-responsive IP for app.publicnode.com: 2606:4700:10::ac42:96a2
The subdomain app.publicnode.com resolves to 2606:4700:10::ac42:96a2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::ac42:96a2 is operational or remove the DNS record for app.publicnode.com.
Non-responsive IP for app.publicnode.com: 2606:4700:10::6814:1875
The subdomain app.publicnode.com resolves to 2606:4700:10::6814:1875 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::6814:1875 is operational or remove the DNS record for app.publicnode.com.
Non-responsive IP for cdn.publicnode.com: 2606:4700:10::6814:1875
The subdomain cdn.publicnode.com resolves to 2606:4700:10::6814:1875 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::6814:1875 is operational or remove the DNS record for cdn.publicnode.com.
Non-responsive IP for cdn.publicnode.com: 2606:4700:10::ac42:96a2
The subdomain cdn.publicnode.com resolves to 2606:4700:10::ac42:96a2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::ac42:96a2 is operational or remove the DNS record for cdn.publicnode.com.
Non-responsive IP for blog.publicnode.com: 2606:4700:10::6814:1875
The subdomain blog.publicnode.com resolves to 2606:4700:10::6814:1875 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::6814:1875 is operational or remove the DNS record for blog.publicnode.com.
Non-responsive IP for blog.publicnode.com: 2606:4700:10::ac42:96a2
The subdomain blog.publicnode.com resolves to 2606:4700:10::ac42:96a2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::ac42:96a2 is operational or remove the DNS record for blog.publicnode.com.
Non-responsive IP for shop.publicnode.com: 2606:4700:10::ac42:96a2
The subdomain shop.publicnode.com resolves to 2606:4700:10::ac42:96a2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::ac42:96a2 is operational or remove the DNS record for shop.publicnode.com.
Non-responsive IP for shop.publicnode.com: 2606:4700:10::6814:1875
The subdomain shop.publicnode.com resolves to 2606:4700:10::6814:1875 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::6814:1875 is operational or remove the DNS record for shop.publicnode.com.
Non-responsive IP for store.publicnode.com: 2606:4700:10::6814:1875
The subdomain store.publicnode.com resolves to 2606:4700:10::6814:1875 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::6814:1875 is operational or remove the DNS record for store.publicnode.com.
Non-responsive IP for store.publicnode.com: 2606:4700:10::ac42:96a2
The subdomain store.publicnode.com resolves to 2606:4700:10::ac42:96a2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::ac42:96a2 is operational or remove the DNS record for store.publicnode.com.
Non-responsive IP for support.publicnode.com: 2606:4700:10::6814:1875
The subdomain support.publicnode.com resolves to 2606:4700:10::6814:1875 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::6814:1875 is operational or remove the DNS record for support.publicnode.com.
Non-responsive IP for support.publicnode.com: 2606:4700:10::ac42:96a2
The subdomain support.publicnode.com resolves to 2606:4700:10::ac42:96a2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::ac42:96a2 is operational or remove the DNS record for support.publicnode.com.
Non-responsive IP for help.publicnode.com: 2606:4700:10::6814:1875
The subdomain help.publicnode.com resolves to 2606:4700:10::6814:1875 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::6814:1875 is operational or remove the DNS record for help.publicnode.com.
Non-responsive IP for help.publicnode.com: 2606:4700:10::ac42:96a2
The subdomain help.publicnode.com resolves to 2606:4700:10::ac42:96a2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::ac42:96a2 is operational or remove the DNS record for help.publicnode.com.
Non-responsive IP for docs.publicnode.com: 2606:4700:10::ac42:96a2
The subdomain docs.publicnode.com resolves to 2606:4700:10::ac42:96a2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::ac42:96a2 is operational or remove the DNS record for docs.publicnode.com.
Non-responsive IP for docs.publicnode.com: 2606:4700:10::6814:1875
The subdomain docs.publicnode.com resolves to 2606:4700:10::6814:1875 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::6814:1875 is operational or remove the DNS record for docs.publicnode.com.
Non-responsive IP for status.publicnode.com: 2606:4700:10::ac42:96a2
The subdomain status.publicnode.com resolves to 2606:4700:10::ac42:96a2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::ac42:96a2 is operational or remove the DNS record for status.publicnode.com.
Non-responsive IP for status.publicnode.com: 2606:4700:10::6814:1875
The subdomain status.publicnode.com resolves to 2606:4700:10::6814:1875 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::6814:1875 is operational or remove the DNS record for status.publicnode.com.
Non-responsive IP for git.publicnode.com: 2606:4700:10::ac42:96a2
The subdomain git.publicnode.com resolves to 2606:4700:10::ac42:96a2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::ac42:96a2 is operational or remove the DNS record for git.publicnode.com.
Non-responsive IP for git.publicnode.com: 2606:4700:10::6814:1875
The subdomain git.publicnode.com resolves to 2606:4700:10::6814:1875 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::6814:1875 is operational or remove the DNS record for git.publicnode.com.
Non-responsive IP for ci.publicnode.com: 2606:4700:10::ac42:96a2
The subdomain ci.publicnode.com resolves to 2606:4700:10::ac42:96a2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::ac42:96a2 is operational or remove the DNS record for ci.publicnode.com.
Non-responsive IP for ci.publicnode.com: 2606:4700:10::6814:1875
The subdomain ci.publicnode.com resolves to 2606:4700:10::6814:1875 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::6814:1875 is operational or remove the DNS record for ci.publicnode.com.
Non-responsive IP for jenkins.publicnode.com: 2606:4700:10::ac42:96a2
The subdomain jenkins.publicnode.com resolves to 2606:4700:10::ac42:96a2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::ac42:96a2 is operational or remove the DNS record for jenkins.publicnode.com.
Non-responsive IP for jenkins.publicnode.com: 2606:4700:10::6814:1875
The subdomain jenkins.publicnode.com resolves to 2606:4700:10::6814:1875 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::6814:1875 is operational or remove the DNS record for jenkins.publicnode.com.
Non-responsive IP for grafana.publicnode.com: 2606:4700:10::ac42:96a2
The subdomain grafana.publicnode.com resolves to 2606:4700:10::ac42:96a2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::ac42:96a2 is operational or remove the DNS record for grafana.publicnode.com.
Non-responsive IP for grafana.publicnode.com: 2606:4700:10::6814:1875
The subdomain grafana.publicnode.com resolves to 2606:4700:10::6814:1875 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::6814:1875 is operational or remove the DNS record for grafana.publicnode.com.
Non-responsive IP for prometheus.publicnode.com: 2606:4700:10::ac42:96a2
The subdomain prometheus.publicnode.com resolves to 2606:4700:10::ac42:96a2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::ac42:96a2 is operational or remove the DNS record for prometheus.publicnode.com.
Non-responsive IP for prometheus.publicnode.com: 2606:4700:10::6814:1875
The subdomain prometheus.publicnode.com resolves to 2606:4700:10::6814:1875 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::6814:1875 is operational or remove the DNS record for prometheus.publicnode.com.
Non-responsive IP for kibana.publicnode.com: 2606:4700:10::6814:1875
The subdomain kibana.publicnode.com resolves to 2606:4700:10::6814:1875 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::6814:1875 is operational or remove the DNS record for kibana.publicnode.com.
Non-responsive IP for kibana.publicnode.com: 2606:4700:10::ac42:96a2
The subdomain kibana.publicnode.com resolves to 2606:4700:10::ac42:96a2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::ac42:96a2 is operational or remove the DNS record for kibana.publicnode.com.
Non-responsive IP for elastic.publicnode.com: 2606:4700:10::ac42:96a2
The subdomain elastic.publicnode.com resolves to 2606:4700:10::ac42:96a2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::ac42:96a2 is operational or remove the DNS record for elastic.publicnode.com.
Non-responsive IP for elastic.publicnode.com: 2606:4700:10::6814:1875
The subdomain elastic.publicnode.com resolves to 2606:4700:10::6814:1875 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:10::6814:1875 is operational or remove the DNS record for elastic.publicnode.com.
No NSEC/NSEC3 records found
Neither NSEC nor NSEC3 records were found. Authenticated denial of existence is not configured.
💡 Configure NSEC3 records for authenticated denial of existence while preventing zone enumeration.
All MX records resolve correctly
No dangling MX records detected — all MX hostnames resolve to valid IP addresses.
Explicit MX records present
The domain has explicit MX records — no implicit A-record fallback delivery.
No internal information leakage detected
No non-routable IP addresses or internal references were found in public DNS records.
No excessive DNS information exposure detected
No HINFO, LOC, RP records, version disclosures, or zone walking vulnerabilities were found.
1 subdomain(s) discovered for publicnode.com
Subdomains were enumerated via Certificate Transparency logs, DNS wordlist brute-forcing, and DNS record analysis.
0 certificate(s) found in CT logs
Certificate Transparency logs contain 0 certificate(s) for publicnode.com and its subdomains. Each certificate reveals subdomain names.
Wildcard DNS record detected
A wildcard DNS record exists for *.publicnode.com, resolving to 172.66.150.162, 104.20.24.117. Wildcard records make subdomain brute-forcing less effective but may mask misconfigurations.
Microsoft Autodiscover endpoint detected
The Autodiscover endpoint at autodiscover.publicnode.com responded with HTTP 404.
DNSSEC is enabled
DNSKEY and/or DS records are present, indicating DNSSEC is configured.
Reputation Findings
Missing domain locks: clientDeleteProhibited
Domain publicnode.com is missing protective locks: clientDeleteProhibited.
💡 Enable clientTransferProhibited and clientDeleteProhibited locks through your registrar to prevent unauthorized transfers or deletions.
Not listed on any DNS blacklists
Domain and MX IPs checked against 55 DNSBLs — no listings found.
HSTS enabled with preload on publicnode.com
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
HSTS enabled with preload on webmail.publicnode.com
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
security.txt present
Found security.txt at https://publicnode.com/.well-known/security.txt.
TLS certificate valid for 41 days
Certificate for publicnode.com expires on 2026-07-09.
Certificate issued by E8
The certificate for publicnode.com is issued by a third-party CA.
Signature algorithm: ecdsa-with-sha384
The certificate for publicnode.com uses an acceptable signature algorithm.
ECC key: 256 bits
The certificate for publicnode.com uses an adequate ECC key of 256 bits.
SCTs present in certificate
The certificate for publicnode.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on publicnode.com.
Domain valid for 79 days
Domain publicnode.com expires on 2026-08-16.
No disposable email provider MX records
MX records for publicnode.com do not match known disposable email provider patterns.
Domain is 3572 days old
Domain publicnode.com was registered 2016-08-16.
No wildcard MX records
No wildcard MX records detected for publicnode.com.
TLD has good reputation
The .com TLD is not on known abuse watchlists.
DMARC reporting destinations look legitimate
DMARC rua/ruf addresses do not point to known URL shortener services.
MX records point to stable infrastructure
No MX records point to known dynamic DNS service domains.
Strong TLS configuration on primary MX
Primary MX (mx.publicnode.com) uses TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 including Forward Secrecy.
SMTP banner matches infrastructure identity
The SMTP banner (mx.allnodes.com) aligns with the MX hostname (mx.publicnode.com).
Google Safe Browsing DNS check — no flag detected
DNS-based Safe Browsing lookup returned no results. Full verification requires the Google Safe Browsing API key.
Abuse contacts found for MX IPs
Abuse contact information retrieved via abusix.org DNS lookup.
PhishTank — API key required
PhishTank phishing database check requires an API key.
Sender Score — API key required
Sender Score reputation check requires an API key.
Cisco Talos — API key required
Cisco Talos IP reputation check requires an API key.
WHOIS registration data
Registrar: Name.com, Inc. | Created: 2016-08-16 | Expires: 2026-08-16 | Updated: 2025-07-19
WHOIS privacy protection enabled
Domain publicnode.com has WHOIS privacy/redaction enabled.
Bulletproof Hosting Detection — API key required
Checking IPs against known bulletproof hosting providers requires a threat intelligence API key.
Threat Intelligence Feeds — API key required
Checking domain against threat intelligence feeds requires API keys (e.g., VirusTotal, AbuseIPDB).
Typosquat detected: publinode.com, publicode.com
2 registered lookalike domain(s) that could be used for phishing against your brand. Domains with MX records can send and receive email, making them high-risk phishing vectors.
Dependency Chains
DMARC Authentication Chain (SPF)
DMARC uses SPF to verify that emails come from authorized servers
SPF Record
SPF record found and configured
→
DMARC Policy
DMARC policy: quarantine
DMARC Authentication Chain (DKIM)
DMARC uses DKIM to verify that emails have not been tampered with
DKIM Signature
DKIM signature missing
→
DMARC Policy
DMARC policy: quarantine
⚠️ DKIM signature is missing. DMARC relies on DKIM to verify email integrity and prevent tampering. Without DKIM, DMARC alignment will fail for cryptographic verification.
Mail Server Identity: mx.publicnode.com
PTR record proves mail server legitimacy
MX: mx.publicnode.com
Mail server at 104.248.94.71
→
PTR Record
Reverse DNS: mx.allnodes.com
Mail Server Reputation: mx.publicnode.com
RBL check ensures server is not blacklisted
MX: mx.publicnode.com
Mail server at 104.248.94.71
→
RBL Status
Not blacklisted
Enforced Encryption Chain
MTA-STS enforces TLS encryption to prevent man-in-the-middle attacks
TLS Support
Mail servers support TLS encryption
→
MTA-STS Policy
MTA-STS not configured
⚠️ MTA-STS policy is missing. Even with TLS support, you lack the enforcement layer that prevents attackers from stripping encryption (downgrade attacks).
Brand Identity Chain
BIMI displays your logo in email clients, but requires DMARC enforcement
DMARC Enforcement
DMARC policy: quarantine
→
BIMI Record
BIMI not configured
⚠️ BIMI record is missing. Even with DMARC enforcement, you need to configure BIMI to display your brand logo in supported email clients.
TLS Monitoring Chain
TLS-RPT provides reports about TLS connection failures
TLS Support
Mail servers support TLS encryption
→
TLS-RPT Reporting
TLS-RPT not configured
⚠️ TLS-RPT is not configured. Without TLS reporting, you have no visibility into TLS connection failures that may be impacting email delivery.
Security Checks
MX Records
✓
SPF Record
✓
DKIM Record
✗
DMARC Policy
✓
BIMI Record
✗
CAA Records
✗
DNSSEC
✓
MTA-STS
✗
TLS-RPT
✗
Embed Badge
Display your domain's security grade on your website or README:
<img src="https://scan.ractermx.com/badge/publicnode.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan publicnode.com Again