Identity
18
F
asuscomm.com
Posture Score: 37/100
Scanned May 30, 2026 at 6:56 AM UTC
Attack Surface
0
Reputation
92
Identity Findings
No SPF record found
The domain has no SPF record, allowing anyone to send email as this domain.
💡 Publish an SPF TXT record (e.g. "v=spf1 include:_spf.google.com -all").
No DMARC record found
The domain has no DMARC record, providing no policy for handling unauthenticated email.
💡 Publish a DMARC TXT record at _dmarc.asuscomm.com (e.g. "v=DMARC1; p=reject; rua=mailto:dmarc@asuscomm.com").
No MX records found
The domain has no MX records and cannot receive email.
💡 Publish MX records pointing to your mail server(s).
Does not meet bulk sender requirements
Google and Yahoo require all bulk senders to have SPF+DKIM, DMARC, and one-click unsubscribe. Issues: Neither SPF nor DKIM is configured (at least one required); No DMARC record published (required since Feb 2024); SPF not published (recommended alongside DKIM)
💡 Publish SPF, DKIM, and DMARC records. Implement RFC 8058 one-click unsubscribe for marketing mail.
Nameserver unresponsive: ns-nw.asuscomm.com
The nameserver ns-nw.asuscomm.com is not responding on port 53.
💡 Verify that ns-nw.asuscomm.com is properly configured and accessible.
No DKIM records found
No DKIM records were found after probing 56 common selectors. The domain may use a custom selector not discoverable via external scan.
💡 Configure DKIM signing and publish the public key at <selector>._domainkey.asuscomm.com
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.asuscomm.com/.well-known/mta-sts.txt
Insufficient nameserver redundancy
Fewer than two nameservers with resolvable IP addresses were found.
💡 Configure at least two nameservers on different network subnets for redundancy.
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@asuscomm.com").
ARC check skipped — no MX records
Cannot assess ARC support without MX records.
Very low TTL on MX record: 120s
The MX record has a TTL of 120s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on TXT record: 60s
The TXT record has a TTL of 60s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on DMARC record: 60s
The DMARC record has a TTL of 60s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
DNS responses are consistent across all nameservers
All authoritative nameservers return consistent answers with proper AA flags.
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.
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.
DANE check skipped — no MX records
Cannot check DANE/TLSA without MX records.
No BIMI record found
BIMI is not configured. Your brand logo will not display in supporting email clients.
Open relay check skipped — no MX records
Cannot test for open relay without MX records.
SMTP compliance check skipped — no MX records
Cannot test SMTP compliance without MX records.
Port exposure check skipped — no MX records
Cannot scan ports without MX records.
Domain is IPv4-only
No AAAA records found for the domain, MX servers, or nameservers. The domain operates on IPv4 only.
STARTTLS downgrade check skipped — no MX records
Cannot test STARTTLS without MX records.
RFC 8058 one-click unsubscribe assessment
No DKIM signing detected. RFC 8058 one-click unsubscribe requires DKIM-signed List-Unsubscribe headers.
FCrDNS check skipped — no MX records
Cannot perform FCrDNS without MX records.
SOA record parameters
Serial: 55, Refresh: 28800s, Retry: 7200s, Expire: 604800s, Min TTL: 30s
Attack Surface Findings
Non-responsive nameserver: ns-nw.asuscomm.com
The nameserver ns-nw.asuscomm.com delegated for asuscomm.com is not responding on port 53. An attacker who gains control of this hostname could hijack the entire zone.
💡 Remove the NS delegation to ns-nw.asuscomm.com or ensure the nameserver is operational.
Dangling MX: hostmaster.asuscomm.com does not resolve
The MX record points to hostmaster.asuscomm.com which has no A record. This may indicate a decommissioned mail provider (Unknown). Attackers can potentially re-register this hostname to hijack inbound mail.
💡 Remove the stale MX record pointing to hostmaster.asuscomm.com or update it to your current mail provider.
Non-routable IPv4 in public DNS: smtp.asuscomm.com → 100.104.24.110
The subdomain smtp.asuscomm.com resolves to non-routable IP 100.104.24.110, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: app.asuscomm.com → 100.118.58.117
The subdomain app.asuscomm.com resolves to non-routable IP 100.118.58.117, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: docs.asuscomm.com → 100.99.224.77
The subdomain docs.asuscomm.com resolves to non-routable IP 100.99.224.77, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-responsive IP for www.asuscomm.com: 240e:35a:71b:f300::2
The subdomain www.asuscomm.com resolves to 240e:35a:71b:f300::2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 240e:35a:71b:f300::2 is operational or remove the DNS record for www.asuscomm.com.
Non-responsive IP for ftp.asuscomm.com: 218.211.38.203
The subdomain ftp.asuscomm.com resolves to 218.211.38.203 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 218.211.38.203 is operational or remove the DNS record for ftp.asuscomm.com.
Non-responsive IP for vpn.asuscomm.com: 2408:8207:5436:3dc0:7e10:c9ff:feb4:d480
The subdomain vpn.asuscomm.com resolves to 2408:8207:5436:3dc0:7e10:c9ff:feb4:d480 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2408:8207:5436:3dc0:7e10:c9ff:feb4:d480 is operational or remove the DNS record for vpn.asuscomm.com.
Non-responsive IP for remote.asuscomm.com: 98.191.7.185
The subdomain remote.asuscomm.com resolves to 98.191.7.185 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 98.191.7.185 is operational or remove the DNS record for remote.asuscomm.com.
Non-responsive IP for admin.asuscomm.com: 2409:8a60:3:37b:6c25:2a63:71c:5bf3
The subdomain admin.asuscomm.com resolves to 2409:8a60:3:37b:6c25:2a63:71c:5bf3 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2409:8a60:3:37b:6c25:2a63:71c:5bf3 is operational or remove the DNS record for admin.asuscomm.com.
Non-responsive IP for portal.asuscomm.com: 61.238.207.179
The subdomain portal.asuscomm.com resolves to 61.238.207.179 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 61.238.207.179 is operational or remove the DNS record for portal.asuscomm.com.
Non-responsive IP for dev.asuscomm.com: 49.203.218.166
The subdomain dev.asuscomm.com resolves to 49.203.218.166 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 49.203.218.166 is operational or remove the DNS record for dev.asuscomm.com.
Non-responsive IP for staging.asuscomm.com: 122.100.194.42
The subdomain staging.asuscomm.com resolves to 122.100.194.42 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 122.100.194.42 is operational or remove the DNS record for staging.asuscomm.com.
Non-responsive IP for test.asuscomm.com: 89.104.16.153
The subdomain test.asuscomm.com resolves to 89.104.16.153 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 89.104.16.153 is operational or remove the DNS record for test.asuscomm.com.
Non-responsive IP for app.asuscomm.com: 100.118.58.117
The subdomain app.asuscomm.com resolves to 100.118.58.117 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 100.118.58.117 is operational or remove the DNS record for app.asuscomm.com.
Non-responsive IP for cdn.asuscomm.com: 27.147.197.234
The subdomain cdn.asuscomm.com resolves to 27.147.197.234 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 27.147.197.234 is operational or remove the DNS record for cdn.asuscomm.com.
Non-responsive IP for blog.asuscomm.com: 88.129.190.176
The subdomain blog.asuscomm.com resolves to 88.129.190.176 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 88.129.190.176 is operational or remove the DNS record for blog.asuscomm.com.
Non-responsive IP for store.asuscomm.com: 5.164.196.172
The subdomain store.asuscomm.com resolves to 5.164.196.172 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 5.164.196.172 is operational or remove the DNS record for store.asuscomm.com.
Non-responsive IP for support.asuscomm.com: 193.107.140.111
The subdomain support.asuscomm.com resolves to 193.107.140.111 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 193.107.140.111 is operational or remove the DNS record for support.asuscomm.com.
Non-responsive IP for help.asuscomm.com: 217.208.112.233
The subdomain help.asuscomm.com resolves to 217.208.112.233 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 217.208.112.233 is operational or remove the DNS record for help.asuscomm.com.
Non-responsive IP for docs.asuscomm.com: 100.99.224.77
The subdomain docs.asuscomm.com resolves to 100.99.224.77 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 100.99.224.77 is operational or remove the DNS record for docs.asuscomm.com.
Non-responsive IP for status.asuscomm.com: 109.226.212.196
The subdomain status.asuscomm.com resolves to 109.226.212.196 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 109.226.212.196 is operational or remove the DNS record for status.asuscomm.com.
Non-responsive IP for git.asuscomm.com: 78.173.242.115
The subdomain git.asuscomm.com resolves to 78.173.242.115 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 78.173.242.115 is operational or remove the DNS record for git.asuscomm.com.
Non-responsive IP for ci.asuscomm.com: 91.152.176.141
The subdomain ci.asuscomm.com resolves to 91.152.176.141 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 91.152.176.141 is operational or remove the DNS record for ci.asuscomm.com.
Non-responsive IP for jenkins.asuscomm.com: 46.98.72.61
The subdomain jenkins.asuscomm.com resolves to 46.98.72.61 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 46.98.72.61 is operational or remove the DNS record for jenkins.asuscomm.com.
Non-responsive IP for grafana.asuscomm.com: 78.92.155.169
The subdomain grafana.asuscomm.com resolves to 78.92.155.169 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 78.92.155.169 is operational or remove the DNS record for grafana.asuscomm.com.
Non-responsive IP for prometheus.asuscomm.com: 188.254.178.28
The subdomain prometheus.asuscomm.com resolves to 188.254.178.28 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 188.254.178.28 is operational or remove the DNS record for prometheus.asuscomm.com.
Non-responsive IP for elastic.asuscomm.com: 94.45.168.114
The subdomain elastic.asuscomm.com resolves to 94.45.168.114 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 94.45.168.114 is operational or remove the DNS record for elastic.asuscomm.com.
Domain enumerability: medium
The domain has moderate enumerability. CT logs and DNS records reveal significant information about the domain structure.
💡 Restrict zone transfers, use NSEC3 instead of NSEC, consider wildcard certificates to reduce CT log exposure, and implement rate limiting on DNS queries.
DNSSEC is not enabled
No DNSKEY or DS records were found. DNS responses are not cryptographically authenticated.
💡 Enable DNSSEC by generating DNSKEY records and publishing DS records at the registrar.
Explicit MX records present
The domain has explicit MX records — no implicit A-record fallback delivery.
No excessive DNS information exposure detected
No HINFO, LOC, RP records, version disclosures, or zone walking vulnerabilities were found.
No email autodiscovery endpoints detected
No Microsoft Autodiscover, Mozilla Autoconfig, or email SRV records were found.
30 subdomain(s) discovered for asuscomm.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 asuscomm.com and its subdomains. Each certificate reveals subdomain names.
Reputation Findings
Missing domain locks: clientDeleteProhibited
Domain asuscomm.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 asuscomm.com
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
security.txt present
Found security.txt at https://asuscomm.com/.well-known/security.txt.
TLS certificate valid for 198 days
Certificate for asuscomm.com expires on 2026-12-14.
Certificate issued by Sectigo Public Server Authentication CA OV R36
The certificate for asuscomm.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for asuscomm.com uses an acceptable signature algorithm.
RSA key: 2048 bits
The certificate for asuscomm.com uses an adequate RSA key of 2048 bits.
SCTs present in certificate
The certificate for asuscomm.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on asuscomm.com.
Domain valid for 2780 days
Domain asuscomm.com expires on 2034-01-08.
No disposable email provider MX records
MX records for asuscomm.com do not match known disposable email provider patterns.
Domain is 7081 days old
Domain asuscomm.com was registered 2007-01-08.
No wildcard MX records
No wildcard MX records detected for asuscomm.com.
TLD has good reputation
The .com TLD is not on known abuse watchlists.
MX records point to stable infrastructure
No MX records point to known dynamic DNS service domains.
Strong TLS configuration on primary MX
Primary MX (hostmaster.asuscomm.com) uses with cipher including Forward Secrecy.
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.
No abuse contacts resolved
Could not resolve abuse contact information for MX IPs via abusix.org.
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.
Could not connect to webmail.asuscomm.com
HTTPS request to https://webmail.asuscomm.com failed or timed out.
WHOIS registration data
Registrar: Net-Chinese Co., Ltd. | Created: 2007-01-08 | Expires: 2034-01-08 | Updated: 2025-06-02
WHOIS privacy protection enabled
Domain asuscomm.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: auscomm.com (has MX!), asscomm.com (has MX!), asuscom.com
3 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 missing
→
DMARC Policy
DMARC policy missing
⚠️ SPF record is missing. DMARC relies on SPF to verify sender authorization. Without SPF, DMARC alignment will fail, reducing email deliverability and brand protection.
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 missing
⚠️ 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: hostmaster.asuscomm.com
PTR record proves mail server legitimacy
MX: hostmaster.asuscomm.com
Mail server at hostmaster.asuscomm.com
→
PTR Record
No PTR record
⚠️ Mail server hostmaster.asuscomm.com (hostmaster.asuscomm.com) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Reputation: hostmaster.asuscomm.com
RBL check ensures server is not blacklisted
MX: hostmaster.asuscomm.com
Mail server at hostmaster.asuscomm.com
→
RBL Status
Not blacklisted
Enforced Encryption Chain
MTA-STS enforces TLS encryption to prevent man-in-the-middle attacks
TLS Support
TLS not verified or unsupported
→
MTA-STS Policy
MTA-STS not configured
⚠️ TLS support could not be verified. MTA-STS requires TLS to enforce encrypted connections. Without TLS, MTA-STS cannot function.
Brand Identity Chain
BIMI displays your logo in email clients, but requires DMARC enforcement
DMARC Enforcement
DMARC not enforced (p=none or missing)
→
BIMI Record
BIMI not configured
⚠️ DMARC is not enforced. BIMI requires a DMARC policy of "quarantine" or "reject" to prove you have strong email authentication. Without enforcement, email clients will not display your logo.
TLS Monitoring Chain
TLS-RPT provides reports about TLS connection failures
TLS Support
TLS not verified or unsupported
→
TLS-RPT Reporting
TLS-RPT not configured
⚠️ TLS support could not be verified. TLS-RPT reports on TLS connection failures, but without TLS support, there's nothing to monitor. You need working TLS encryption before TLS-RPT can provide value.
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/asuscomm.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan asuscomm.com Again