Artgotham.com ⇒ DNS Record Check

DNS & IP Record Check for Artgotham.com

This tool gives you a detailed look at Artgotham.com DNS setup. It checks various parts of the DNS records to ensure everything is functioning smoothly and securely.

DNS Record Group Breakdown:

Our DNS & IP record check is organized into 6 main groups, each focusing on different aspects of your domain's DNS configuration. Each group tests key components to ensure optimal domain performance:

DNS Parent Group - 5 tests
NS (Nameserver) - 17 tests
SOA (Start of Authority) - 9 tests
MX (Mail Exchanger) - 12 tests
MAIL (Email) - 4 tests
WWW (World Wide Web) - 24 tests

Test Status Summary:

To help you better understand the results, our team has categorized the outcomes into four statuses:

PASS - No issues found in the DNS record.
FAIL - We detected a DNS record error that needs your attention.
WARN - A minor DNS record issue was found.
INFO - Informational data about the DNS record with no errors detected.

To ensure the integrity and security of Artgotham.com DNS data, use our DNSSEC check tool. This test provides a deeper analysis, focusing on digital signatures, security, and integrity of the DNS records.

Below is an overview of the results from our comprehensive DNS lookup for the domain Artgotham.com:

DNS Group

DNS Check

DNS Record Type

DNS Data Information

PARENT

PASS

Missing Direct Parent check

OK. Your direct parent zone exists, SOA of parent zone com is a.gtld-servers.net which is good. Some domains (usually third or fourth level domains, such as example.co.us or subdomain.example.co.us) do not have a direct parent zone ('co.us' in this example), which is legal but can cause confusion.

PASS

Glue at parent nameservers

OK. The parent servers have glue for your nameservers. That means they send out the IP address of your nameservers, as well as their host names

INFO

NS records at parent servers

Your NS record at parent servers are:

dns101.register.com	[IP Address=162.159.24.117]	[TTL=172800]
dns102.register.com	[IP Address=162.159.25.158]	[TTL=172800]

These were obtained from k.gtld-servers.net. However these were obtained from authority section and not answer section. It is better if they were obtained from answer section.

PASS

DNS servers have A records

OK. All your DNS servers either have A records at the zone parent servers

PASS

Parent nameservers have your nameservers listed

OK. When someone uses DNS to look up your domain, the first step (if it doesn't already know about your domain) is to go to the parent servers. If you aren't listed there, you can't be found. But you are listed there.

DNS Group

DNS Status

DNS Record Type

DNS Data Information

INFO

NS records at your nameservers

Your NS records at your nameservers are:

dns101.register.com		[TTL=14400]
dns102.register.com		[TTL=14400]

PASS

Mismatched NS records

OK. NS records at all your nameservers are identical.

PASS

All nameservers respond

All your nameservers responding.

PASS

Recursive queries

None of your nameservers allow recursive queries

PASS

Zone Transfer

Zone transfer not allowed by any of your nameservers

PASS

No NS A records at nameservers

OK. Your nameservers do include corresponding A records when asked for your NS records. This ensures that your DNS servers know the A records corresponding to all your NS records.

PASS

Nameserver name validity

OK. All of the NS records that your nameservers report seem valid (no IPs or partial domain names).

PASS

Number of nameservers

You have 2 nameservers. You must have at least 2 nameservers (RFC2182 section 5 recommends at least 3 nameservers), and preferably no more than 7.

PASS

Lame nameservers

OK. All the nameservers listed at the parent servers answer authoritatively for your domain.

PASS

Missing (stealth) nameservers

You have no stealth servers.

PASS

Missing nameservers 2

All nameservers listed at parent servers are listed as NS records at your nameservers

PASS

No CNAMEs for domain

OK. There are no CNAMEs for Artgotham.com. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.

PASS

TCP Allowed

All your nameservers allow TCP connection

PASS

Stealth NS record leakage

Your DNS servers doesn't leak NS record in non-NS request.

PASS

Nameservers on separate class C's

OK. You have nameservers on different Class C (technically, /24) IP ranges. You must have nameservers at geographically and topologically dispersed locations. RFC2182 3.1 goes into more detail about secondary nameserver location.

PASS

All NS IPs public

OK. All of your NS records appear to use public IPs. If there were any private IPs, they would not be reachable, causing DNS delays.

FAIL

Glue for NS record

Your nameservers for your NS records didn't return the A records for the NS records.

DNS Group	DNS Status	DNS Record Type	DNS Data Information
SOA
	INFO	SOA record	Your SOA record [TTL=] is: Primary Name server: Hostmaster E-mail address: Serial #: Refresh: Retry: Expire: Default:
	FAIL	SOA MNAME entry	SOA MNAME is not listed as a primary nameserver at your parent nameserver
	FAIL	SOA RNAME entry	OK. valid SOA rname record not found
	PASS	NS agreement on SOA Serial #	OK. All your nameservers agree that your SOA serial number is 2009050102. That means that all your nameservers are using the same data (unless you have different sets of data with the same serial number, which would be very bad)! Note that the DNS report only checks the NS records listed at the parent servers (not any stealth servers).
	FAIL	SOA Serial	Your SOA serial number is: . This doesn't appears to be in the recommended format of YYYYMMDDnn.
	FAIL	SOA REFRESH	Your SOA REFRESH interval is: . That is not right
	FAIL	SOA RETRY	OK. Your SOA RETRY interval is: . That is not right
	FAIL	SOA EXPIRE	Your SOA EXPIRE interval is: . That is not right
	PASS	SOA MINIMUM TTL	Your SOA MINIMUM TTL is: . That is not right

DNS Group	DNS Status	DNS Record Type	DNS Data Information
MX
	FAIL	MX Glue	MX record look up did not send glue record for atleast 1 MX server: alt1.aspmx.l.google.com, alt4.aspmx.l.google.com, alt3.aspmx.l.google.com, alt2.aspmx.l.google.com, mx07.register.com, aspmx.l.google.com
	PASS	MX records are not CNAMEs	OK. Looking up your MX record did not just return a CNAME. If an MX record query returns a CNAME, extra processing is required, and some mail servers may not be able to handle it.
	PASS	MX name validity	Good. We did not detect any invalid chars in hostnames for your MX records.
	PASS	MX is host name, not IP	OK. All of your MX records are host names (as opposed to IP addresses, which are not allowed in MX records).
	PASS	Different MX records at nameservers	Good. Looks like all your nameservers have the same set of MX records. This tests to see if there are any MX records not reported by all your nameservers
	FAIL	MX Glues match	MX Glue returned by nameserver for MX record doesn't match with A record of MX hostname alt1.aspmx.l.google.com > 209.85.144.26;///// X alt4.aspmx.l.google.com > 108.177.123.26;///// X alt3.aspmx.l.google.com > 192.178.218.27;///// X alt2.aspmx.l.google.com > 108.177.11.27;///// X mx07.register.com > 209.17.115.10;///// X aspmx.l.google.com > 64.233.185.27;///// X
	PASS	Duplicate MX records	OK. You do not have any duplicate MX records (pointing to the same IP). Although technically valid, duplicate MX records can cause a lot of confusion, and waste resources.
	PASS	MX A lookups have no CNAMEs	OK. There appear to be no CNAMEs returned for A records lookups from your MX records (CNAMEs are prohibited in MX records, according to RFC974, RFC1034 3.6.2, RFC1912 2.4, and RFC2181 10.3).
	INFO	MX Record	Your 6 records: 5 alt1.aspmx.l.google.com [IP Address=209.85.144.26] [TTL=3600] 10 alt4.aspmx.l.google.com [IP Address=108.177.123.26] [TTL=3600] 10 alt3.aspmx.l.google.com [IP Address=192.178.218.27] [TTL=3600] 5 alt2.aspmx.l.google.com [IP Address=108.177.11.27] [TTL=3600] 10 mx07.register.com [IP Address=209.17.115.10] [TTL=14400] 1 aspmx.l.google.com [IP Address=64.233.185.27] [TTL=3600]
	PASS	Multiple MX records	OK. You have multiple MX records. This means that if one is down or unreachable, the other(s) will be able to accept mail for you.
	PASS	Reverse MX A records (PTR)	The reverse (PTR) record for your MX records: 209.85.144.26 -> qv-in-f26.1e100.net 108.177.123.26 -> lcscld-in-f26.1e100.net 192.178.218.27 -> yuiadtq-in-f27.1e100.net 108.177.11.27 -> vz-in-f27.1e100.net 209.17.115.10 -> mx.myregisteredsite.com 64.233.185.27 -> yb-in-f27.1e100.net
	PASS	All MX IPs public	OK. All of your MX records appear to use public IPs. If there were any private IPs, they would not be reachable, causing slight mail delays, extra resource usage, and possibly bounced mail.

DNS Group	DNS Status	DNS Record Type	DNS Data Information
MAIL
	PASS	SPF record	v=spf1 include:spf.registeredsite.com -all google-site-verification=EFeBitaXtVvtrzvL79pWqUItZd-8Nmrv2khlk9rQr4g this domain sends email from following domains/subdomains:spf.registeredsite.com
	WARN	Sender ID record(spfv2.0)	SenderID framework not implemented
	WARN	Domain Key Test	Domain keys not implemenetd for _domainkey.Artgotham.com. Separate domainkey records may exist for subdomains and selectors under this domain. this cannot be tested.
	WARN	DMARC	DMARC policy not found. Not enabled.

DNS Group	DNS Status	DNS Record Type	DNS Data Information
WWW
	INFO	WWW A record	Your WWW A record is: www.Artgotham.com > shops.myshopify.com. Resolved IP: 23.227.38.74 Your WWW is CNAME record and your CNAME entry returns A record which is good. WA & DA Score for shops.myshopify.com
	PASS	IPs are public	OK. All of your WWW IP addresses appear to be public IP addresses.
	PASS	HTTP Service	OK: We can connect to http service on port 80.
	INFO	Server	http service on port 80 returns server information as Cloudflare
	PASS	Server Header	http response header returns information about server as: Cloudflare
	PASS	Connection	http connection header return connection as: Keep-alive
	PASS	Secure Header HSTS	The server implemented the HSTS (HTTP Strict Transport Security) policy by adding a header over the HTTPS connection as: Max-age=7889238
	PASS	Secure Header X-Frame-Options	XFO response header that protects against clickjacking is found as: DENY XFO enables content to be found or not within iframes via the browser.
	PASS	Secure Header X-Content-Type-Options	The secure X-Content-Type-Options header is set as: Nosniff The browser must interpret the file exactly as it is specified in the Content-Type HTTP header
	PASS	Secure Header Content-Security-Policy	The return secure header sends feedback that the CSP has been found and specified. CSP is defined in the policy as: Block-all-mixed-content; frame-ancestors 'none'; upgrade-insecure-requests; CSP prevents various types of attacks, such as cross-site scripting and other types of cross-site injection
	PASS	Secure Header X-Permitted-Cross-Domain-Policies	X-Permitted-Cross-Domain-Policies is found in the response header as: None X-Permitted-Cross-Domain-Policies is an XML file that gives a web client permission to handle data across domains.
	WARN	Secure Header Referrer-Policy	The Referrer-Policy HTTP header is not set, as it is not in the Referrer header.
	INFO	Secure Header Clear-Site-Data	Clear-Site-Data was not found in the response header
	INFO	Secure Header Cross-Origin-Embedder-Policy	COEP response header was not found in the HTTP request
	INFO	Secure Header Cross-Origin-Opener-Policy	COOP response header was not found in the HTTP request
	WARN	Secure Header Cross-Origin-Resource-Policy	CORP policy not found in response header
	WARN	Secure Header Cache-Control	Cache-Control policy header not found in HTTP responses
	WARN	Secure Header Permissions-Policy	Permissions-Policy header was not found in the HTTP responses.
	INFO	Secure Header Feature-Policy	Feature-Policy header was not found in the HTTP responses.
	PASS	Secure Header X-XSS-Protection (Deprecated)	X-XSS-Protection header is found in the HTTP response.as: 1; mode=block X-XSS-Protection sets up a scripting filter in your browser.
	INFO	Secure Header HTTP Public Key Pinning (Deprecated)	HPKP header was not found in the HTTP responses.
	INFO	Secure Header Expect-CT (Deprecated)	Expect-CT header was not found in the HTTP responses.
	PASS	SSL / HTTPS Protocol	Domain use encrypted SSL / HTTPS connection on port 443. View SSL Certificate: Artgotham.com.
	FAIL	IPv6	Your domain has no IPv6 support

Click below to copy URL to clipboard for easy sharing of results: