Check DNS, Urls + Redirects, Certificates and Content of your Website

...

skip EDNS-Check

skip Content-Check

check links

DNS-problem - authoritative Nameserver refused, not defined or timeout

Checked:
09.05.2025 20:28:38

Older results

No older results found

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
verisign-grs.com	A		yes	1	0
	AAAA		yes
www.verisign-grs.com			yes	2	2
*.verisign-grs.com	A	Name Error	yes
	AAAA	Name Error	yes
	CNAME	Name Error	yes

2. DNSSEC

Zone (*)	DNSSEC - Informations

Zone: (root)
(root)	1 DS RR published


	DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest 4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=


	• Status: Valid because published


	3 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 20326, Flags 257 (SEP = Secure Entry Point)


	Public Key with Algorithm 8, KeyTag 38696, Flags 257 (SEP = Secure Entry Point)


	Public Key with Algorithm 8, KeyTag 53148, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 22.05.2025, 00:00:00 +, Signature-Inception: 01.05.2025, 00:00:00 +, KeyTag 20326, Signer-Name: (root)


	• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 20326 used to validate the DNSKEY RRSet


	• Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest "4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: com
com	1 DS RR in the parent zone found


	DS with Algorithm 13, KeyTag 19718, DigestType 2 and Digest isuwzSj0ElCoCkkTiUJNNBUi2Uaw2gwCkfLT13HXgFo=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 22.05.2025, 17:00:00 +, Signature-Inception: 09.05.2025, 16:00:00 +, KeyTag 53148, Signer-Name: (root)


	• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 53148 used to validate the DS RRSet in the parent zone


	2 DNSKEY RR found


	Public Key with Algorithm 13, KeyTag 19718, Flags 257 (SEP = Secure Entry Point)


	Public Key with Algorithm 13, KeyTag 40097, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner com., Algorithm: 13, 1 Labels, original TTL: 86400 sec, Signature-expiration: 17.05.2025, 14:02:35 +, Signature-Inception: 02.05.2025, 13:57:35 +, KeyTag 19718, Signer-Name: com


	• Status: Good - Algorithmus 13 and DNSKEY with KeyTag 19718 used to validate the DNSKEY RRSet


	• Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 19718, DigestType 2 and Digest "isuwzSj0ElCoCkkTiUJNNBUi2Uaw2gwCkfLT13HXgFo=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: verisign-grs.com
verisign-grs.com	1 DS RR in the parent zone found


	DS with Algorithm 8, KeyTag 2102, DigestType 2 and Digest HcVzA+heMTGF2qQaqXDBYCxGE+CIz/7ALbYVcDH3YSY=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner verisign-grs.com., Algorithm: 13, 2 Labels, original TTL: 86400 sec, Signature-expiration: 13.05.2025, 02:04:40 +, Signature-Inception: 06.05.2025, 00:54:40 +, KeyTag 40097, Signer-Name: com


	• Status: Good - Algorithmus 13 and DNSKEY with KeyTag 40097 used to validate the DS RRSet in the parent zone


	2 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 2102, Flags 257 (SEP = Secure Entry Point)


	Public Key with Algorithm 8, KeyTag 48564, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner verisign-grs.com., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 07.06.2025, 23:18:43 +, Signature-Inception: 08.05.2025, 23:18:43 +, KeyTag 2102, Signer-Name: verisign-grs.com


	• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 2102 used to validate the DNSKEY RRSet


	• Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 2102, DigestType 2 and Digest "HcVzA+heMTGF2qQaqXDBYCxGE+CIz/7ALbYVcDH3YSY=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone


	RRSIG Type 16 validates the TXT - Result: v=spf1 include:spf-i.verisign.com include:spf-p.verisign.com ~all Validated: RRSIG-Owner verisign-grs.com., Algorithm: 8, 2 Labels, original TTL: 300 sec, Signature-expiration: 07.06.2025, 23:18:43 +, Signature-Inception: 08.05.2025, 23:18:43 +, KeyTag 48564, Signer-Name: verisign-grs.com


	RRSIG Type 257 validates the CAA - Result: 5\|issuedigicert.com Validated: RRSIG-Owner verisign-grs.com., Algorithm: 8, 2 Labels, original TTL: 300 sec, Signature-expiration: 07.06.2025, 23:18:43 +, Signature-Inception: 08.05.2025, 23:18:43 +, KeyTag 48564, Signer-Name: verisign-grs.com


	A-Query sends a valid NSEC3 RR as result with the hashed query name "duj7a3kfi1cee90o998b0ssfrsj8bu41" equal the hashed NSEC3-owner "duj7a3kfi1cee90o998b0ssfrsj8bu41" and the hashed NextOwner "duqrdle26rv4m5djne35tqjmqraj339l". So the zone confirmes the not-existence of that A RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: NS, SOA, MX, TXT, RRSIG, DNSKEY, NSEC3PARAM, CAA Validated: RRSIG-Owner duj7a3kfi1cee90o998b0ssfrsj8bu41.verisign-grs.com., Algorithm: 8, 3 Labels, original TTL: 5 sec, Signature-expiration: 07.06.2025, 23:18:43 +, Signature-Inception: 08.05.2025, 23:18:43 +, KeyTag 48564, Signer-Name: verisign-grs.com


	Status: Good. NoData-Proof required and found.


	CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "duj7a3kfi1cee90o998b0ssfrsj8bu41" equal the hashed NSEC3-owner "duj7a3kfi1cee90o998b0ssfrsj8bu41" and the hashed NextOwner "duqrdle26rv4m5djne35tqjmqraj339l". So the zone confirmes the not-existence of that CNAME RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: NS, SOA, MX, TXT, RRSIG, DNSKEY, NSEC3PARAM, CAA Validated: RRSIG-Owner duj7a3kfi1cee90o998b0ssfrsj8bu41.verisign-grs.com., Algorithm: 8, 3 Labels, original TTL: 5 sec, Signature-expiration: 07.06.2025, 23:18:43 +, Signature-Inception: 08.05.2025, 23:18:43 +, KeyTag 48564, Signer-Name: verisign-grs.com


	Status: Good. NoData-Proof required and found.


	AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "duj7a3kfi1cee90o998b0ssfrsj8bu41" equal the hashed NSEC3-owner "duj7a3kfi1cee90o998b0ssfrsj8bu41" and the hashed NextOwner "duqrdle26rv4m5djne35tqjmqraj339l". So the zone confirmes the not-existence of that AAAA RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: NS, SOA, MX, TXT, RRSIG, DNSKEY, NSEC3PARAM, CAA Validated: RRSIG-Owner duj7a3kfi1cee90o998b0ssfrsj8bu41.verisign-grs.com., Algorithm: 8, 3 Labels, original TTL: 5 sec, Signature-expiration: 07.06.2025, 23:18:43 +, Signature-Inception: 08.05.2025, 23:18:43 +, KeyTag 48564, Signer-Name: verisign-grs.com


	Status: Good. NoData-Proof required and found.


	TLSA-Query (_443._tcp.verisign-grs.com) sends a valid NSEC3 RR as result with the hashed owner name "duj7a3kfi1cee90o998b0ssfrsj8bu41" (unhashed: verisign-grs.com). So that's the Closest Encloser of the query name. Bitmap: NS, SOA, MX, TXT, RRSIG, DNSKEY, NSEC3PARAM, CAA Validated: RRSIG-Owner duj7a3kfi1cee90o998b0ssfrsj8bu41.verisign-grs.com., Algorithm: 8, 3 Labels, original TTL: 5 sec, Signature-expiration: 07.06.2025, 23:18:43 +, Signature-Inception: 08.05.2025, 23:18:43 +, KeyTag 48564, Signer-Name: verisign-grs.com


	Status: Good. NXDomain-Proof required and found.


	TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "l05hbsh0vu3di4il5no2qfkth1qlmkih" (unhashed: _tcp.verisign-grs.com) with the owner "kvmqva5acmqv26bo0mme0i64gmfke1i4" and the NextOwner "l1mj2jml15cp6p34rgsokrhh6ufrr68n". So that NSEC3 confirms the not-existence of the Next Closer Name. Bitmap: A, RRSIG Validated: RRSIG-Owner kvmqva5acmqv26bo0mme0i64gmfke1i4.verisign-grs.com., Algorithm: 8, 3 Labels, original TTL: 5 sec, Signature-expiration: 07.06.2025, 23:18:43 +, Signature-Inception: 08.05.2025, 23:18:43 +, KeyTag 48564, Signer-Name: verisign-grs.com


	Status: Good. NXDomain-Proof required and found.


	TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Wildcard expansion of the ClosestEncloser "8dppb9btkkj7l4b36b75hva4l0laivf8" (unhashed: *.verisign-grs.com) with the owner "8bi24p0giu0fn9j679lm7dlciib3aokc" and the NextOwner "8envcq3epht4drunae4gtpl79mb2amq5". So that NSEC3 confirms the not-existence of the Wildcard expansion. Bitmap: No Bitmap? Validated: RRSIG-Owner 8bi24p0giu0fn9j679lm7dlciib3aokc.verisign-grs.com., Algorithm: 8, 3 Labels, original TTL: 5 sec, Signature-expiration: 07.06.2025, 23:18:43 +, Signature-Inception: 08.05.2025, 23:18:43 +, KeyTag 48564, Signer-Name: verisign-grs.com


	Status: Good. NXDomain-Proof required and found.

Zone: www.verisign-grs.com
www.verisign-grs.com	0 DS RR in the parent zone found


	DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed query name "sieh0fkbutbhfo905d7qu4nvdtmnd948" between the hashed NSEC3-owner "sieh0fkbutbhfo905d7qu4nvdtmnd948" and the hashed NextOwner "skg95t99i3j8keg7o1huh89k8n4roabp". So the parent zone confirmes the not-existence of a DS RR. Bitmap: No Bitmap? Validated: RRSIG-Owner sieh0fkbutbhfo905d7qu4nvdtmnd948.verisign-grs.com., Algorithm: 8, 3 Labels, original TTL: 5 sec, Signature-expiration: 07.06.2025, 23:18:43 +, Signature-Inception: 08.05.2025, 23:18:43 +, KeyTag 48564, Signer-Name: verisign-grs.com

3. Name Servers

Domain	Nameserver	NS-IP
www.verisign-grs.com	T ns33.verisign.com
	T ns8.verisign.com
verisign-grs.com	• av1.nstld.com / nnn1-defra-4	192.42.177.30 Miami/Florida/United States (US) - VeriSign Infrastructure & Operations	•
	•	2001:500:124::30 Sterling/Virginia/United States (US) - VeriSign Infrastructure & Operations	•
	• av2.nstld.com / nnn1-nlams-4	192.42.178.30 Reston/Virginia/United States (US) - VeriSign Inc.	•
	•	2001:500:125::30 Amsterdam/North Holland/The Netherlands (NL) - VeriSign Inc.	•
	• av3.nstld.com / nnn1-ham2	192.82.133.30 Reston/Virginia/United States (US) - VeriSign Inc.	•
	•	2001:500:126::30 New York/United States (US) - VeriSign Inc.	•
	• av4.nstld.com / nnn1-defra-4	192.82.134.30 New York/United States (US) - VeriSign Inc.	•
	•	2001:500:127::30 New York/United States (US) - VeriSign Inc.	•
com	• a.gtld-servers.net / nnn1-par6		•
	• b.gtld-servers.net / nnn1-eltxl1		•
	• c.gtld-servers.net / nnn1-par6		•
	• d.gtld-servers.net / nnn1-par6		•
	• e.gtld-servers.net / nnn1-par6		•
	• f.gtld-servers.net / nnn1-defra-4		•
	• g.gtld-servers.net / nnn1-defra-4		•
	• h.gtld-servers.net / nnn1-defra-4		•
	• i.gtld-servers.net / nnn1-defra-4		•
	• j.gtld-servers.net / nnn1-frmrs-2		•
	• k.gtld-servers.net / nnn1-frmrs-2		•
	• l.gtld-servers.net / nnn1-frmrs-2		•
	• m.gtld-servers.net / nnn1-frmrs-2		•

4. SOA-Entries

Domain:	com
Zone-Name:	com
Primary:	a.gtld-servers.net
Mail:	nstld.verisign-grs.com
Serial:	1746815290
Refresh:	1800
Retry:	900
Expire:	604800
TTL:	900
num Entries:	7

Domain:	com
Zone-Name:	com
Primary:	a.gtld-servers.net
Mail:	nstld.verisign-grs.com
Serial:	1746815310
Refresh:	1800
Retry:	900
Expire:	604800
TTL:	900
num Entries:	6

Domain:	verisign-grs.com
Zone-Name:	verisign-grs.com
Primary:	av1.nstld.com
Mail:	mdnshelp.verisign.com
Serial:	1746749924
Refresh:	300
Retry:	7200
Expire:	1209600
TTL:	5
num Entries:	8

Domain:	www.verisign-grs.com
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:	2

5. Screenshots

No Screenshot listed, because no url-check with https + http status 200-299, 400-599 + not-ACME-check found.

6. Url-Checks

Domainname	Http-Status	redirect	Sec.	G
•

7. Comments

	1. General Results, most used to calculate the result
A	name "verisign-grs.com" is domain, public suffix is ".com", top-level-domain is ".com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .com-domains preloaded: 105479 (complete: 270180)
	HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
X	Fatal error: Nameserver doesn't support TCP connection: ns33.verisign.com: Timeout
X	Fatal error: Nameserver doesn't support TCP connection: ns8.verisign.com: Timeout
B	No _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Read the result of server-daten.de (Url-Checks, Comments, Connections and DomainServiceRecords) to see a complete definition. Domainname: _mta-sts.verisign-grs.com
	2. Header-Checks
U		No https result with http status 2 or 4 (standard-check) found, no header checked.
	3. DNS- and NameServer - Checks
A	Info:: 2 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers.
A	Info:: 2 Queries complete, 2 with IPv6, 0 with IPv4.
A	Good: All DNS Queries done via IPv6.
A	Good: Some ip addresses of name servers found with the minimum of two DNS Queries. One to find the TLD-Zone, one to ask the TLD-Zone.av1.nstld.com (192.42.177.30, 2001:500:124::30), av2.nstld.com (192.42.178.30, 2001:500:125::30), av3.nstld.com (192.82.133.30, 2001:500:126::30), av4.nstld.com (192.82.134.30, 2001:500:127::30)
A	Good (1 - 3.0):: An average of 0.5 queries per domain name server required to find all ip addresses of all name servers.
A	Info:: 4 different Name Servers found: av1.nstld.com, av2.nstld.com, av3.nstld.com, av4.nstld.com, 4 Name Servers included in Delegation: av1.nstld.com, av2.nstld.com, av3.nstld.com, av4.nstld.com, 4 Name Servers included in 1 Zone definitions: av1.nstld.com, av2.nstld.com, av3.nstld.com, av4.nstld.com, 1 Name Servers listed in SOA.Primary: av1.nstld.com.
A	Good: Only one SOA.Primary Name Server found.: av1.nstld.com.
A	Good: SOA.Primary Name Server included in the delegation set.: av1.nstld.com.
A	Good: Consistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Ordered list of name servers: av1.nstld.com, av2.nstld.com, av3.nstld.com, av4.nstld.com
A	Good: All Name Server Domain Names have a Public Suffix.
A	Good: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
A	Good: All Name Server ip addresses are public.
A	Good: Minimal 2 different name servers (public suffix and public ip address) found: 4 different Name Servers found
A	Good: All name servers have ipv4- and ipv6-addresses.: 4 different Name Servers found
	Warning: All Name Servers have the same Top Level Domain / Public Suffix. If there is a problem with that Top Level Domain, your domain may be affected. Better: Use Name Servers with different top level domains.: 4 Name Servers, 1 Top Level Domain: com
	Warning: All Name Servers have the same domain name. If there is a problem with that domain name (or with the name servers of that domain name), your domain may be affected. Better: Use Name Servers with different domain names / different top level domains.: Only one domain name used: nstld.com
A	Good: Name servers with different Country locations found: 4 Name Servers, 2 Countries: NL, US
A	Info: Ipv4-Subnet-list: 4 Name Servers, 1 different subnets (first Byte): 192., 2 different subnets (first two Bytes): 192.42., 192.82., 4 different subnets (first three Bytes): 192.42.177., 192.42.178., 192.82.133., 192.82.134.
A	Good: Name Server IPv4-addresses from different subnet found:
A	Info: IPv6-Subnet-list: 4 Name Servers with IPv6, 1 different subnets (first block): 2001:, 1 different subnets (first two blocks): 2001:0500:, 4 different subnets (first three blocks): 2001:0500:0124:, 2001:0500:0125:, 2001:0500:0126:, 2001:0500:0127:, 4 different subnets (first four blocks): 2001:0500:0124:0000:, 2001:0500:0125:0000:, 2001:0500:0126:0000:, 2001:0500:0127:0000:
A	Good: Name Server IPv6 addresses from different subnets found.
A	Good: Nameserver supports TCP connections: 8 good Nameserver
A	Good: Nameserver supports Echo Capitalization: 8 good Nameserver
X	Nameserver Timeout checking Echo Capitalization: ns33.verisign.com
X	Nameserver Timeout checking Echo Capitalization: ns8.verisign.com
A	Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 8 good Nameserver
X	Nameserver Timeout checking EDNS512: ns33.verisign.com
X	Nameserver Timeout checking EDNS512: ns8.verisign.com
A	Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 8 good Nameserver
	Nameserver doesn't pass all EDNS-Checks: ns33.verisign.com: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
	Nameserver doesn't pass all EDNS-Checks: ns8.verisign.com: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
A	Good: All SOA have the same Serial Number
A	Good: CAA entries found, creating certificate is limited: digicert.com is allowed to create certificates
	4. Content- and Performance-critical Checks
A	Good: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx
A	Duration: 225913 milliseconds, 225.913 seconds

8. Connections

No connection informations found. Perhaps only http - connections.

9. Certificates

No certificate informations found. Perhaps only http - connections.

10. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates (one check per day)

No CertSpotter - CT-Log entries found

2. Source crt.sh - old and new certificates, sometimes very slow - only certificates with "not after" > of the last months are listed

No CRT - CT-Log entries found

11. Html-Content - Entries

No Html-Content entries found. Only checked if https + status 200/401/403/404

12. Html-Parsing via https://validator.w3.org/nu/

No https result http status 200 and Content-Type text/html or text/xml found, no Html-Parsing - Check

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: av1.nstld.com, av2.nstld.com, av3.nstld.com, av4.nstld.com

QNr.	Domain	Type	NS used
1	com	NS	d.root-servers.net (2001:500:2d::d)
	Answer: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net
2	av1.nstld.com: 192.42.177.30, 2001:500:124::30	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: av2.nstld.com 192.42.178.30, 2001:500:125::30
	Answer: av3.nstld.com 192.82.133.30, 2001:500:126::30
	Answer: av4.nstld.com 192.82.134.30, 2001:500:127::30

14. CAA - Entries

Domainname	flag	Name	Value	∑ Queries	∑ Timeout
www.verisign-grs.com				2	2
verisign-grs.com	5	issue	digicert.com	1	0
com	0		no CAA entry found	1	0

15. TXT - Entries

Domainname	TXT Entry	Status	∑ Queries
verisign-grs.com	v=spf1 include:spf-i.verisign.com include:spf-p.verisign.com ~all	ok	1
_acme-challenge.verisign-grs.com		Name Error - The domain name does not exist	1
_acme-challenge.verisign-grs.com.verisign-grs.com		Name Error - The domain name does not exist	1

16. DomainService - Entries

Type		Domain	Pref	Value	DNS-error	num Answers	Status	Description
MX		verisign-grs.com	10	mail1.verisign.com	0	6	ok
	A			72.13.63.30	0	1	ok
	CNAME				0	0	ok
MX		verisign-grs.com	10	mail3.verisign.com	0	6	ok
	A			72.13.63.32	0	1	ok
	CNAME				0	0	ok
MX		verisign-grs.com	10	mail5.verisign.com	0	6	ok
	A			69.58.187.31	0	1	ok
	CNAME				0	0	ok
MX		verisign-grs.com	10	mail6.verisign.com	0	6	ok
	A			69.58.187.32	0	1	ok
	CNAME				0	0	ok
MX		verisign-grs.com	10	mail2.verisign.com	0	6	ok
	A			72.13.63.31	0	1	ok
	CNAME				0	0	ok
MX		verisign-grs.com	10	mail4.verisign.com	0	6	ok
	A			69.58.187.30	0	1	ok
	CNAME				0	0	ok
SPF	TXT	verisign-grs.com		v=spf1 include:spf-i.verisign.com include:spf-p.verisign.com ~all			ok
	TXT	spf-i.verisign.com		v=spf1 ip4:72.13.45.0/25 ip4:69.58.176.0/25 ip4:69.58.186.0/25 ip4:72.13.32.0/25 ip4:72.13.36.0/25 ip4:69.58.178.0/25 ip4:217.30.90.0/25 ip4:69.58.177.0/25 ip4:69.58.187.0/25 ip4:72.13.63.0/25 ip4:198.41.3.0/27 ip4:69.58.179.0/27 ip4:217.30.89.0/27 ip4:216.168.239.0/25 ip4:209.112.118.0/24 ip4:209.112.117.0/24 ip4:72.13.60.15 ip4:63.77.90.11 ip4:209.9.239.15 ip4:81.19.61.10 ~all			ok
	TXT	spf-p.verisign.com		v=spf1 include:_spf.salesforce.com include:sendgrid.net include:_spf.qualtrics.com include:res.cisco.com ~all			ok
	TXT	_spf.salesforce.com		v=spf1 exists:%{i}._spf.mta.salesforce.com -all			ok
	TXT	sendgrid.net		v=spf1 ip4:167.89.0.0/17 ip4:208.117.48.0/20 ip4:50.31.32.0/19 ip4:198.37.144.0/20 ip4:198.21.0.0/21 ip4:192.254.112.0/20 ip4:168.245.0.0/17 ip4:149.72.0.0/16 ip4:159.183.0.0/16 include:ab.sendgrid.net ~all			ok
	TXT	_spf.qualtrics.com		v=spf1 ip4:162.247.216.0/22 ip4:139.60.152.0/22 ip4:98.97.248.0/21 ip4:64.69.212.0/24 ip4:54.186.193.102/32 ip4:52.222.73.120/32 ip4:52.222.73.83 ip4:52.222.62.51 ip4:52.222.75.85 ip4:52.222.89.228 ip4:160.1.62.192 ip4:52.61.91.9 ip4:15.200.21.50 ip4:15.200.201.185 ip4:15.200.44.248 -all			ok
	TXT	res.cisco.com		v=spf1 mx:res.cisco.com exists:%{i}.spf.res.cisco.com -all			ok
	TXT	ab.sendgrid.net		v=spf1 ip4:223.165.113.0/24 ip4:223.165.115.0/24 ip4:223.165.118.0/23 ip4:223.165.120.0/23 ~all			ok
	MX	res.cisco.com		esa1.cres.iphmx.com			ok
	MX-A	esa1.cres.iphmx.com		68.232.140.79			ok
	MX	res.cisco.com		esa2.cres.iphmx.com			ok
	MX-A	esa2.cres.iphmx.com		68.232.140.57			ok
	MX	res.cisco.com		esa3.cres.iphmx.com			ok
	MX-A	esa3.cres.iphmx.com		68.232.135.234			ok
	MX	res.cisco.com		esa4.cres.iphmx.com			ok
	MX-A	esa4.cres.iphmx.com		68.232.135.235			ok
_dmarc	TXT	_dmarc.verisign-grs.com		v=DMARC1; p=reject; pct=100; rua=mailto:verisign@rua.agari.com,mailto:mailreports@verisign.com!10m; ruf=mailto:verisign@ruf.agari.com,mailto:mailauthfail@verisign.com!10m; rf=afrf; ri=86400			ok
	TXT	verisign-grs.com._report._dmarc.rua.agari.com		mailto:verisign@rua.agari.com			ok	Mail domain unequal current domain. Check required, if there is a confirming _report._dmarc-Record. See RFC 7489, 7.1.
	TXT	verisign-grs.com._report._dmarc.verisign.com		mailto:mailreports@verisign.com			ok	Mail domain unequal current domain. Check required, if there is a confirming _report._dmarc-Record. See RFC 7489, 7.1.
	TXT	verisign-grs.com._report._dmarc.rua.agari.com		v=DMARC1;			ok	Confirmed. Sending reports to external domain is allowed.
	TXT	verisign-grs.com._report._dmarc.verisign.com					16	Domainname not defined: NXDOMAIN. Report not sent.
	TXT	verisign-grs.com._report._dmarc.ruf.agari.com		mailto:verisign@ruf.agari.com			ok	Mail domain unequal current domain. Check required, if there is a confirming _report._dmarc-Record. See RFC 7489, 7.1.
	TXT	verisign-grs.com._report._dmarc.verisign.com		mailto:mailauthfail@verisign.com			ok	Mail domain unequal current domain. Check required, if there is a confirming _report._dmarc-Record. See RFC 7489, 7.1.
	TXT	verisign-grs.com._report._dmarc.ruf.agari.com		v=DMARC1;			ok	Confirmed. Sending reports to external domain is allowed.
	TXT	verisign-grs.com._report._dmarc.verisign.com					16	Domainname not defined: NXDOMAIN. Report not sent.

17. Cipher Suites

No Ciphers found

18. Portchecks

No open Ports <> 80 / 443 found, so no additional Ports checked.

Permalink: https://check-your-website.server-daten.de/?i=22f882d7-00e7-42e4-aebd-27dd7df22967

Last Result: https://check-your-website.server-daten.de/?q=verisign-grs.com - 2025-05-09 20:28:38

Do you like this page? Support this tool, add a link on your page:

<a href="https://check-your-website.server-daten.de/?q=verisign-grs.com" target="_blank">Check this Site: verisign-grs.com</a>

Do you really want to support this project? Donate: Check-your-website, IBAN DE98 1001 0010 0575 2211 07, SWIFT/BIC PBNKDEFF, Euro

QR-Code of this page - https://check-your-website.server-daten.de/?d=verisign-grs.com