Report for samsung.com

Report created on: Wed, 24 Apr 2024 11:11:59 GMT

Parent		100
NS		14
SOA		77
MX		100
Mail		13
Web		100

NS Records at Parent Servers

We have successfully fetched domain's NS records from parent name server (h.gtld-servers.net.).
Domain NS records:

dns-awskr1.samsung.com. TTL=172800 [52.79.211.80] [NO GLUE6]
dns-gi1.samsung.com. TTL=172800 [203.241.132.185] [NO GLUE6]
dnssm.samsung.com. TTL=172800 [203.241.132.51] [NO GLUE6]
dnssm2.samsung.com. TTL=172800 [112.107.53.58] [NO GLUE6]
dnsst.samsung.com. TTL=172800 [203.241.135.51] [NO GLUE6]
dnsst2.samsung.com. TTL=172800 [112.106.53.58] [NO GLUE6]

Missing Glue

OK. Parent name servers are offering glue for domain's name servers. We received name servers list and it's IP addresses from parent name server (h.gtld-servers.net.).

Name Servers Have A Records

OK. Found A records for all name servers.

dns-awskr1.samsung.com. → 52.79.211.80
dns-gi1.samsung.com. → 203.241.132.185
dnssm.samsung.com. → 203.241.132.51
dnssm2.samsung.com. → 112.107.53.58
dnsst.samsung.com. → 203.241.135.51
dnsst2.samsung.com. → 112.106.53.58

To reach your name servers via IPv4 an A record is needed for each name server.

Name Servers Have AAAA Records

NOTICE: While reading domain NS records at parent name servers, we found name servers without AAAA records.

dns-awskr1.samsung.com. → ?
dns-gi1.samsung.com. → ?
dnssm.samsung.com. → 2001:330:a:300a:203:241:132:51
dnssm2.samsung.com. → 2001:330:a:300b:112:107:53:58
dnsst.samsung.com. → 2001:330:a:a:203:241:135:51
dnsst2.samsung.com. → 2001:330:a:b:112:106:53:58

To reach your name servers via IPv6 an AAAA record is needed for each name server.

NS Records

Your name servers returned 15 NS records:

auth01.nhn.ic. TTL=300 [NO GLUE4] [NO GLUE6]
auth01.sam.ic. TTL=300 [NO GLUE4] [NO GLUE6]
auth02.nhn.ic. TTL=300 [NO GLUE4] [NO GLUE6]
auth02.sam.ic. TTL=300 [NO GLUE4] [NO GLUE6]
auth03.nhn.ic. TTL=300 [NO GLUE4] [NO GLUE6]
auth03.sam.ic. TTL=300 [NO GLUE4] [NO GLUE6]
auth04.nhn.ic. TTL=300 [NO GLUE4] [NO GLUE6]
auth04.sam.ic. TTL=300 [NO GLUE4] [NO GLUE6]
dns-awskr1.samsung.com. TTL=300 [NO GLUE4] [NO GLUE6]
dns-gi1.samsung.com. TTL=300 [NO GLUE4] [NO GLUE6]
dns-gi2.samsung.com. TTL=300 [NO GLUE4] [NO GLUE6]
dnssm.samsung.com. TTL=300 [NO GLUE4] [NO GLUE6]
dnssm2.samsung.com. TTL=300 [NO GLUE4] [NO GLUE6]
dnsst.samsung.com. TTL=300 [NO GLUE4] [NO GLUE6]
dnsst2.samsung.com. TTL=300 [NO GLUE4] [NO GLUE6]

All Name Servers Responded

FAIL: While quering domain's records, some of your name servers didn't responded. Name servers which didn't responded:

udp6:2001:330:a:b:112:106:53:58
udp6:2001:330:a:300b:112:107:53:58

Glue Check

OK. No differences found. The glue provided by the parent name servers has to match the data provided by the authoritative name servers.

Allow Recursive Queries

OK. Domain name servers are not allowing recursive queries. On all name servers which acts as caching name servers recursive queries should be restricted to local networks. Having open DNS servers can lead to abuses such as cache poisoning and DOS (denial of service) attacks. Cache poisoning attacks allows under certain conditions to redirect legitimate web traffic, email and other traffic to malicious hosts compromising security.

Check Name Servers Count

OK. Domain has 15 name servers. Recommended number, between 2 and 7 name servers (RFC 2182 recommends to have at least 3 authoritative name servers for domains).

Identical NS Records

OK. All your name servers reported identical NS records. Each name server should return identical NS records.

Check for Lame Name servers

OK. No lame name servers found. All of your name servers are configured to be either master or slave for your domain.

Check All IPs are Public

OK. No private IPs found. Name servers using private IPs can't be reached from the Internet causing DNS delays.

Name Servers Have A Records

FAIL: We found name servers without A records.

auth01.nhn.ic. → ?
auth01.sam.ic. → ?
auth02.nhn.ic. → ?
auth02.sam.ic. → ?
auth03.nhn.ic. → ?
auth03.sam.ic. → ?
auth04.nhn.ic. → ?
auth04.sam.ic. → ?
dns-awskr1.samsung.com. → 52.79.211.80
dns-gi1.samsung.com. → 203.241.132.185
dns-gi2.samsung.com. → 203.241.135.186, 203.241.132.185, 203.241.135.185
dnssm.samsung.com. → 203.241.132.51
dnssm2.samsung.com. → 112.107.53.58
dnsst.samsung.com. → 203.241.135.51
dnsst2.samsung.com. → 112.106.53.58

To reach your name servers via IPv4 an A record is needed for each name server.

Name Servers Have AAAA Records

NOTICE: We found name servers without AAAA records.

auth01.nhn.ic. → ?
auth01.sam.ic. → ?
auth02.nhn.ic. → ?
auth02.sam.ic. → ?
auth03.nhn.ic. → ?
auth03.sam.ic. → ?
auth04.nhn.ic. → ?
auth04.sam.ic. → ?
dns-awskr1.samsung.com. → ?
dns-gi1.samsung.com. → ?
dns-gi2.samsung.com. → ?
dnssm.samsung.com. → 2001:330:a:300a:203:241:132:51
dnssm2.samsung.com. → 2001:330:a:300b:112:107:53:58
dnsst.samsung.com. → 2001:330:a:a:203:241:135:51
dnsst2.samsung.com. → 2001:330:a:b:112:106:53:58

To reach your name servers via IPv6 an AAAA record is needed for each name server.

Name Servers Have Valid Names

OK. All names are valid. Name server name should be a valid host name, no partial name or IP address.

Check for Stealth Name Servers

WARNING: Found stealth name servers:

auth01.nhn.ic.
auth01.sam.ic.
auth02.nhn.ic.
auth02.sam.ic.
auth03.nhn.ic.
auth03.sam.ic.
auth04.nhn.ic.
auth04.sam.ic.
dns-gi2.samsung.com.

All name servers returned by domain name servers should be listed at parent servers.

Check for Missing Name Servers

OK. No missing name servers found. All name servers returned by the parent name servers should have an NS record at your name servers.

No CNAME in NS Records

OK. No CNAMEs found in NS records. RFC 2181, section 10.3 says that host name must map directly to one or more address record (A or AAAA) and must not point to any CNAME records. RFC 1034, section 3.6.2 says if a name appears in the right-hand side of RR (Resource Record) it should not appear in the left-hand name of CNAME RR, thus CNAME records should not be used with NS and MX records. Despite this restrictions, there are many working configuration using CNAME with NS and MX records.

Allow TCP connections

WARNING: Couldn't connect using TCP protocol:

tcp6:2001:330:a:b:112:106:53:58
tcp6:2001:330:a:300b:112:107:53:58

Check your name server's configurations and firewall rules. When response to a DNS query exceeds 512 bytes, TCP is negotiated and used, all name servers should allow TCP connections (port 53).

Name Servers Distributed on Multiple Networks

OK. Name servers are dispersed on 5 different C class networks:

112.106.53.0/24:
- dnsst2.samsung.com.
112.107.53.0/24:
- dnssm2.samsung.com.
203.241.132.0/24:
- dns-gi1.samsung.com.
- dns-gi2.samsung.com.
- dnssm.samsung.com.
203.241.135.0/24:
- dns-gi2.samsung.com.
- dns-gi2.samsung.com.
- dnsst.samsung.com.
52.79.211.0/24:
- dns-awskr1.samsung.com.

Name servers should be dispersed (topologically and geographically) across the Internet to avoid risk of single point of failure (RFC 2182).

Name Servers Distributed on Multiple ASNs

OK. Name servers are dispersed on 2 different Autonomous Systems:

AS6619:
- dns-gi1.samsung.com.
- dns-gi2.samsung.com.
- dnssm.samsung.com.
- dnssm2.samsung.com.
- dnsst.samsung.com.
- dnsst2.samsung.com.
AS16509:
- dns-awskr1.samsung.com.

Name servers should be dispersed (topologically and geographically) across the Internet to avoid risk of single point of failure (RFC 2182).

Name Servers Versions

OK. Name servers software versions are not exposed:

112.106.53.58: "unknown"
112.107.53.58: "unknown"
2001:330:a:300a:203:241:132:51: "unknown"
2001:330:a:300b:112:107:53:58: "unknown"
2001:330:a:a:203:241:135:51: "unknown"
2001:330:a:b:112:106:53:58: "unknown"
203.241.132.185: "unknown"
203.241.132.51: "unknown"
203.241.135.185: "unknown"
203.241.135.186: "unknown"
203.241.135.51: "unknown"
52.79.211.80: "unknown"

Exposing name server's versions may be risky, when a new vulnerability is found your name servers may be automatically exploited by script kiddies until you patch the system. Learn how to hide version.

Check SOA Record

Domain SOA Record:

Primary nameserver: gm.sam.ic.
Hostmaster (e-mail): ssdomain.samsung.com.
Serial: 2020083024
Refresh: 10800
Retry: 3600
Expire: 2419200
Minimum TTL: 300

Name Servers Agreement on Serial Number

WARNING: We found different serial numbers on your name servers, it's OK if you had modified your zone recently.

112.106.53.58: 2020083024
112.107.53.58: 2020083024
2001:330:a:300a:203:241:132:51: 2020083024
2001:330:a:300b:112:107:53:58: 0
2001:330:a:a:203:241:135:51: 2020083024
2001:330:a:b:112:106:53:58: 0
203.241.132.185: 2020083024
203.241.132.51: 2020083024
203.241.135.51: 2020083024
52.79.211.80: 2020083024

Having different serials on your name servers may show inconsistencies between name servers configuration (multiple masters), or communication errors (ACL and firewall issues).

SOA Number Format

OK. Serial number format OK [2020083024]. Your serial number is following general convention for serial number YYYYMMDDnn, where YYYY is four-digit year number, MM is the month, DD is the day and nn is the sequence number in case zone file is updated more than once per day.

SOA Mname

WARNING: Primary name server gm.sam.ic. listed in SOA Record is not found at the parent name servers. The MNAME field defines the Primary Master name server for the zone, this name server should be found in your NS records.

SOA Rname

OK. Contact email for DNS problems is [email protected]. (ssdomain.samsung.com.). RNAME field defines an administrative email for your zone. RFC2142 recommends using hostmaster e-mail for this purpose, but any valid e-mail address can be used.

SOA Refresh

OK. Refresh interval is 10800. Recommended values [1200 .. 43200] (20 min ... 12 hours). Refresh field from SOA record determines how quickly zone changes are propagated from master to slave.

SOA Retry

OK. Retry interval is 3600. Recommended values [120 .. 7200] (2 minutes .. 2 hours). Retry field from SOA record defines how often slave should retry contacting master if connection to master failed during refresh.

SOA Expire

WARNING: Expire interval is 2419200. Recommended values [604800 .. 1209600] (1 week ... 2 weeks). Expiry defines zone expiration time in seconds after which slave must re-validate zone file, if contacting master fails then slave will stop responding to any queries.

SOA Minimum TTL

WARNING: Minimum TTL value is 300. Recommended values [3600 .. 86400] (1 hour ... 1 day). Minimum TTL was redefined in RFC 2308, now it defines the period of time used by slaves to cache negative responses.

MX Records

Your name servers returned 1 MX records:

10 mailin.samsung.com. TTL=300

Identical MX Records

OK. All name servers returned identical MX records.

Mail Servers Have A Records

OK. Found A records for all mail servers.

mailin.samsung.com. → 203.254.224.12

To reach your mail servers via IPv4 an A record is needed for each mail server.

Mail Servers Have AAAA Records

NOTICE: While reading domain NS records at parent mail servers, we found mail servers without AAAA records.

mailin.samsung.com. → ?

To reach your mail servers via IPv6 an AAAA record is needed for each mail server.

Reverse Entries for MX records

OK. All mail servers have reverse DNS entries configured correctly.

	Server	IP	PTR (Reverse)	IPs
	mailin.samsung.com.	203.254.224.12	mailin.samsung.com.	203.254.224.12

All mail servers should have a reverse DNS (PTR) entry for each IP address (RFC 1912). Missing reverse DNS entries will make many mail servers to reject your e-mails or mark them as SPAM.

All IP's reverse DNS entries should resolve back to IP address (IP → PTR → IP). Many mail servers are configured to reject e-mails from IPs with inconsistent reverse DNS configuration.

Check MX Records for Invalid Chars

OK. No invalid characters found. Name field from MX records should be a valid host name.

Check MX Records IPs are Public

OK. No private IPs found. Mail servers using private IPs can't be reached from the Internet causing mail delivery delays.

Check MX Records for Duplicates

OK. No MX records duplicates (same IP addresses) found. Although technically valid, duplicate MX records have no benefits and can cause confusion.

Only Host Names in MX Records

OK. No IPs found in MX records. IP addresses are not allowed in MX records, only host names.

No CNAME in MX Records

OK. No CNAMEs found in MX records. RFC 2181, section 10.3 says that host name must map directly to one or more address record (A or AAAA) and must not point to any CNAME records. RFC 1034, section 3.6.2 says if a name appears in the right-hand side of RR (Resource Record) it should not appear in the left-hand name of CNAME RR, thus CNAME records should not be used with NS and MX records. Despite this restrictions, there are many working configuration using CNAME with NS and MX records.

RBL Check

OK. Mail servers IPs are not blacklisted.

Check Google Apps Settings

Test ignored, domain is not using Google Apps.

Connect to Mail Servers

FAIL: Connection to all mail servers failed.

mailin.samsung.com.: Server checks disabled due complaints.

To receive emails, mail servers should allow TCP connections on port 25.

Mail Greeting

OK. No differences between mail server host names and greeting host name.

Accepts Postmaster Address

Temporary error, could not determine if all mail servers are accepting emails to [email protected] address:

mailin.samsung.com.
```
Server checks disabled due complaints.
```

RFC 822, RFC 1123 and RFC 2821 requires that all domain's mail servers should accept e-mails to postmaster. To be compliant you can create an alias and forward all postmaster's e-mails to a valid mailbox.

Accepts Abuse Address

Temporary error, could not determine if all mail servers are accepting emails to [email protected] address:

mailin.samsung.com.
```
Server checks disabled due complaints.
```

Check SPF record

WARNING: Domain doesn't have SPF record. SPF (Sender Policy Framework) record is designed to prevent e-mail spoofing. Typical SPF record would be:
v=spf1 a mx ~all or v=spf1 a mx include:_spf.google.com ~all if you are using Google Apps.

Identical TXT records

FAIL: Your name servers returned different TXT records:

112.106.53.58 →
112.107.53.58 →
203.241.132.185 → google-site-verification=XioIPzfjKziFDv7svS2vFxobJ1j6ApORgnD43-La5jc pardot848313=56b423327c6bbcc73c4888f1e7a74aa35be107baa0d8dbc0d60d3078016cdedb pardot1061362=d72ade8848a288815d8cd7fcdedf8e2ea1ffdf37f2e6199b9c6d2b118b260b11 pardot1061372=cd7a8dc7dac11576e3160df3645c3be60beb48d38262fe75e1b83b6ed4547e2f pardot1061382=ee554f6d1abf83530c2b3bd50be47bc5e417bb833dc9b2686e5c5c384d2e174c
203.241.132.51 → pardot848313=94e68189fc6e698e53ab66f68f9fa66f68b14ab1837bac98f0a5b5b4dd57503d v=spf1 include:_spf.samsung.com ~all asv=8c95d437a5f5281bf0b46412ea6410ff globalsign-domain-verification=9382b64f06fad76d1ebac344380ab28b cisco-ci-domain-verification=37f06378ba0e1526ad9a057438e3f2a1d0888e4e21d4ce75160ac7475679e080 miro-verification=16f39e2d161837f1d97cfb17ff7e81f243c68683
203.241.135.51 → cisco-ci-domain-verification=37f06378ba0e1526ad9a057438e3f2a1d0888e4e21d4ce75160ac7475679e080 miro-verification=16f39e2d161837f1d97cfb17ff7e81f243c68683 7029addd-cf82-4d9e-9ac6-45cd3e47e467 globalsign-domain-verification=d7cac74e387872153b45a1cf21f819ee docusign=022189ea-ba76-432a-abd7-19343970da7e globalsign-domain-verification=BF9A67D3968C1D5FEC1440B12347B6AF
52.79.211.80 → dtm-domain-verification=sj6QpVm4qndJLuG0vmv2lv2WLlZ3g1EGLq9OItKaBQI google-site-verification=XioIPzfjKziFDv7svS2vFxobJ1j6ApORgnD43-La5jc pardot848313=56b423327c6bbcc73c4888f1e7a74aa35be107baa0d8dbc0d60d3078016cdedb pardot1061362=d72ade8848a288815d8cd7fcdedf8e2ea1ffdf37f2e6199b9c6d2b118b260b11 pardot1061372=cd7a8dc7dac11576e3160df3645c3be60beb48d38262fe75e1b83b6ed4547e2f

Only SPF records are compared, all name servers should return identical SPF records.

Identical SPF records

No SPF type records found. All name servers should return identical SPF records.

Check DMARC record

OK. Found DMARC record:

v=DMARC1; p=none; rua=mailto:[email protected]; ruf=mailto:[email protected]

DMARC (Domain-based Message Authentication, Reporting & Conformance) helps reducing potential of email-based abuse such as spam and phishing e-mails.

Resolve Domain Name

OK. Domain samsung.com. resolves to:

211.45.27.231

Domain Name IPs are Public

OK. No private IPs found for samsung.com.. Web servers using private IPs can't be reached from the Internet.

Resolve WWW

OK. Domain www.samsung.com. resolves to:

23.35.28.61

WWW IPs are Public

OK. No private IPs found for www.samsung.com.. Web servers using private IPs can't be reached from the Internet.

Report completed in 12.55 seconds.

Recent reports: telkomsel.com pitchaero.com microsoft.com stanpol.nl stanpolmusic.com