SurfaceMap › s › sify.com

sify.com

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

Domain & DNS

fail

22 passed 3 warn 1 failed

Areas

iRegistration !Delegation ✗Nameservers ✓SOA !DNSSEC iRecords

Problems

  • ✗
    No DNS over TCP
    Nameservers · DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: pdns.satyam.net.in (202.144.63.4): dial tcp 202.144.63.4:53: connect: connection refused; pdns.satyam.net.in (2001:e48:9584::a): read tcp [2a01:4f8:1c1c:eebf::1]:45184->[2001:e48:9584::a]:53: read: connection reset by peer; sdns.satyam.net.in (202.144.63.12): dial tcp 202.144.63.12:53: connect: connection refused; sdns.satyam.net.in (2001:e48:9584::a): EOF.
    #19
  • !
    Nameservers in one network
    Delegation · all IPv4 addresses are in 202.144.63.0/24; all IPv6 addresses are in 2001:e48:9584::/48. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • !
    No EDNS
    Nameservers · These nameservers don't support EDNS(0), needed for DNSSEC and answers larger than 512 bytes: pdns.satyam.net.in (202.144.63.4), pdns.satyam.net.in (2001:e48:9584::a), sdns.satyam.net.in (202.144.63.12), sdns.satyam.net.in (2001:e48:9584::a).
    #20
  • !
    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

Recent checks

✗

Full report

Domain & DNS report for sify.com ›

Mail

fail

15 passed 4 warn 2 failed

Areas

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

Problems

  • ✗
    No DMARC record
    DMARC · No DMARC record was found for this domain. DMARC is essential for preventing email spoofing. Add a DMARC record with p=reject or at least p=quarantine.
    #5
  • ✗
    No DKIM keys published
    DKIM · _domainkey.sify.com does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    Addresses without reverse DNS
    MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 52.101.137.2 (sify-com.mail.protection.outlook.com), 2a01:111:f403:cc09::1 (sify-com.mail.protection.outlook.com). Ask your hosting provider to set one.
    #30
  • !
    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 sify.com ›