SurfaceMap › s › segye.com

segye.com

Checked 2026-10-22 10:40 UTC · first added 2026-10-21
✗Problems found Score 57 of 100

Domain & DNS

warn

22 passed 5 warn 0 failed

Areas

iRegistration !Delegation !Nameservers !SOA !DNSSEC !Records

Problems

  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: ns1-1.ns-ncloud.com, ns1-2.ns-ncloud.com; only in the zone: a13-67.akam.net, a20-67.akam.net, a7-64.akam.net. a1-190.akam.net, a13-67.akam.net, a20-67.akam.net, a26-65.akam.net, a4-67.akam.net, a7-64.akam.net report NS a1-190.akam.net a13-67.akam.net a20-67.akam.net a26-65.akam.net a4-67.akam.net a7-64.akam.net. ns1-1.ns-ncloud.com, ns1-2.ns-ncloud.com report NS ns1-1.ns-ncloud.com ns1-2.ns-ncloud.com.
    #7
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: a1-190.akam.net: "41824.6"; a1-190.akam.net: "41824.11"; a13-67.akam.net: "41824.6"; a20-67.akam.net: "48878.30"; a20-67.akam.net: "48878.33"; a26-65.akam.net: "48878.32"; a26-65.akam.net: "48878.31"; a4-67.akam.net: "48878.27"; a4-67.akam.net: "48878.33"; a7-64.akam.net: "41824.4"; a7-64.akam.net: "41824.8". Hide or replace the version string.
    #17
  • !
    Serials differ
    SOA · The nameservers serve different versions of the zone: 2025022553 on a1-190.akam.net (193.108.91.190), a1-190.akam.net (2600:1401:2::be), a13-67.akam.net (2.22.230.67), a13-67.akam.net (2600:1480:800::43), a20-67.akam.net (95.100.175.67), a20-67.akam.net (2a02:26f0:67::43), a26-65.akam.net (23.74.25.65), a26-65.akam.net (2600:1480:b800::41), a4-67.akam.net (72.246.46.67), a4-67.akam.net (2600:1480:9000::43), a7-64.akam.net (23.61.199.64), a7-64.akam.net (2600:1406:32::40); 243 on ns1-1.ns-ncloud.com (49.236.156.6), ns1-2.ns-ncloud.com (49.236.157.6). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.
    #22
  • !
    Not signed
    DNSSEC · The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27
  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (1m), MX (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 1h; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for segye.com ›

Mail

fail

17 passed 6 warn 1 failed

Areas

✓SPF ✗DMARC !DKIM !DNSSEC !MX !TLS iBIMI

Problems

  • ✗
    Policy: none (monitoring only)
    DMARC · DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • !
    No key under common selectors
    DKIM · The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #7
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Hosts without IP addresses
    MX · The following MX hosts could not be resolved to IP addresses: mail.segye.com
    #10
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: vw.segye.com, mail.segye.com
    #11
  • !
    No aggregate reports (rua)
    DMARC · DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19
  • !
    Not configured
    TLS · MTA-STS is not configured, so other mail servers fall back to unencrypted delivery when TLS fails or is stripped by an attacker. Publish a _mta-sts TXT record and a policy at https://mta-sts.<domain>/.well-known/mta-sts.txt.
    #32

Recent checks

✗

Full report

Mail report for segye.com ›