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

0 in Queue, 0 of max. 8 Checks (09:10:00)
Why should you only use Prefix - Cookies? |
Hall of Fame - A+ and A

 

Shortcuts: 1. IP-Addresses | 2. DNSSEC | 3. Name Servers | 4. SOA-Entries | 5. Screenshots | 6. Url-Checks | 7. Comments | 8. Connections | 9. Certificates | 10. CT-Logs | 11. Html-Content | 12. Html-Parsing | 13. NameServer-IPAddresses | 14. CAA | 15. TXT | 16. DomainServiceEntries | 17. Cipher Suites | 18. Portchecks |

 

T

 

Timeout

 

Checked:
09.05.2025 19:51:08

 

Older results

No older results found

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
u3.verisigndns.com
A
43.247.170.1
Chiyoda/Tokyo/Japan (JP) - Tiggee LLC
Hostname: ns31.constellix.com
yes
1
0

AAAA
2600:180c:3001::1
Herndon/Virginia/United States (US) - Tiggee LLC

yes


www.u3.verisigndns.com

Name Error
yes
1
0
*.verisigndns.com
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


*.u3.verisigndns.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: verisigndns.com

verisigndns.com
1 DS RR in the parent zone found






DS with Algorithm 8, KeyTag 40574, DigestType 2 and Digest 0EU1Ydn3mcmvOFRVp7HOo8drAde656BXX9cLCpaG23g=






1 RRSIG RR to validate DS RR found






RRSIG-Owner verisigndns.com., Algorithm: 13, 2 Labels, original TTL: 86400 sec, Signature-expiration: 13.05.2025, 01:47:31 +, Signature-Inception: 06.05.2025, 00:37:31 +, 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 29691, Flags 256






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






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner verisigndns.com., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 07.06.2025, 23:19:30 +, Signature-Inception: 08.05.2025, 23:19:30 +, KeyTag 40574, Signer-Name: verisigndns.com






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






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



Zone: u3.verisigndns.com

u3.verisigndns.com
0 DS RR in the parent zone found






DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "u3.verisigndns.com" and the NextOwner "www.verisigndns.com". So the parent zone confirmes the non-existence of a DS RR.
Bitmap: A, AAAA, RRSIG, NSEC






0 DNSKEY RR found












RRSIG Type 1 validates the A - Result: 43.247.170.1
Validated: RRSIG-Owner u3.verisigndns.com., Algorithm: 8, 3 Labels, original TTL: 180 sec, Signature-expiration: 07.06.2025, 23:19:30 +, Signature-Inception: 08.05.2025, 23:19:30 +, KeyTag 29691, Signer-Name: verisigndns.com






RRSIG Type 28 validates the AAAA - Result: 2600:180C:3001:0000:0000:0000:0000:0001
Validated: RRSIG-Owner u3.verisigndns.com., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 07.06.2025, 23:19:30 +, Signature-Inception: 08.05.2025, 23:19:30 +, KeyTag 29691, Signer-Name: verisigndns.com






CNAME-Query sends a valid NSEC RR as result with the query name "u3.verisigndns.com" equal the NSEC-owner "u3.verisigndns.com" and the NextOwner "www.verisigndns.com". 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: A, AAAA, RRSIG, NSEC Validated: RRSIG-Owner u3.verisigndns.com., Algorithm: 8, 3 Labels, original TTL: 86400 sec, Signature-expiration: 07.06.2025, 23:19:30 +, Signature-Inception: 08.05.2025, 23:19:30 +, KeyTag 29691, Signer-Name: verisigndns.com






Status: Good. NoData-Proof required and found.






TXT-Query sends a valid NSEC RR as result with the query name "u3.verisigndns.com" equal the NSEC-owner "u3.verisigndns.com" and the NextOwner "www.verisigndns.com". So the zone confirmes the not-existence of that TXT RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, AAAA, RRSIG, NSEC Validated: RRSIG-Owner u3.verisigndns.com., Algorithm: 8, 3 Labels, original TTL: 86400 sec, Signature-expiration: 07.06.2025, 23:19:30 +, Signature-Inception: 08.05.2025, 23:19:30 +, KeyTag 29691, Signer-Name: verisigndns.com






Status: Good. NoData-Proof required and found.






TLSA-Query (_443._tcp.u3.verisigndns.com) sends a valid NSEC RR as result with the owner name u3.verisigndns.com. So that's the Closest Encloser of the query name. TLSA-Query sends a valid NSEC RR as result and covers the Wildcard expansion of the ClosestEncloser with the owner "u3.verisigndns.com" and the NextOwner "www.verisigndns.com". So that NSEC confirms the not-existence of the Wildcard expansion. TLSA-Query (_443._tcp.u3.verisigndns.com) sends a valid NSEC RR as result with the query name "_443._tcp.u3.verisigndns.com" between the NSEC-owner "u3.verisigndns.com" and the NextOwner "www.verisigndns.com". So the zone confirmes the not-existence of that TLSA RR.TLSA-Query (_443._tcp.u3.verisigndns.com) sends a valid NSEC RR as result with the parent Wildcard "*._tcp.u3.verisigndns.com" between the NSEC-owner "u3.verisigndns.com" and the NextOwner "www.verisigndns.com". So the zone confirmes the not-existence of that Wildcard-expansion.
Bitmap: A, AAAA, RRSIG, NSEC Validated: RRSIG-Owner u3.verisigndns.com., Algorithm: 8, 3 Labels, original TTL: 86400 sec, Signature-expiration: 07.06.2025, 23:19:30 +, Signature-Inception: 08.05.2025, 23:19:30 +, KeyTag 29691, Signer-Name: verisigndns.com






Status: Good. NXDomain-Proof required and found.






CAA-Query sends a valid NSEC RR as result with the query name "u3.verisigndns.com" equal the NSEC-owner "u3.verisigndns.com" and the NextOwner "www.verisigndns.com". So the zone confirmes the not-existence of that CAA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, AAAA, RRSIG, NSEC Validated: RRSIG-Owner u3.verisigndns.com., Algorithm: 8, 3 Labels, original TTL: 86400 sec, Signature-expiration: 07.06.2025, 23:19:30 +, Signature-Inception: 08.05.2025, 23:19:30 +, KeyTag 29691, Signer-Name: verisigndns.com






Status: Good. NoData-Proof required and found.



Zone: www.u3.verisigndns.com

www.u3.verisigndns.com
0 DS RR in the parent zone found






DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "u3.verisigndns.com" and the NextOwner "www.verisigndns.com". So the parent zone confirmes the non-existence of a DS RR.
Bitmap: A, AAAA, RRSIG, NSEC

 

3. Name Servers

DomainNameserverNS-IP
www.u3.verisigndns.com
•  av1.nstld.com

u3.verisigndns.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		•
verisigndns.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-wie5
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:1746813050
Refresh:1800
Retry:900
Expire:604800
TTL:900
num Entries:11


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


Domain:verisigndns.com
Zone-Name:verisigndns.com
Primary:av1.nstld.com
Mail:dnssupport.verisign-grs.com
Serial:1746749971
Refresh:28800
Retry:7200
Expire:1209600
TTL:86400
num Entries:8


Domain:u3.verisigndns.com
Zone-Name:verisigndns.com
Primary:av1.nstld.com
Mail:dnssupport.verisign-grs.com
Serial:1746749971
Refresh:28800
Retry:7200
Expire:1209600
TTL:86400
num Entries:2


Domain:www.u3.verisigndns.com
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


5. Screenshots

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

 

 

6. Url-Checks

DomainnameHttp-StatusredirectSec.G
• http://u3.verisigndns.com/
43.247.170.1
-14


10.030
T
Timeout - The operation has timed out.

• http://u3.verisigndns.com/
2600:180c:3001::1
-14


10.020
T
Timeout - The operation has timed out.

• https://u3.verisigndns.com/
43.247.170.1
-14


10.016
T
Timeout - The operation has timed out.

• https://u3.verisigndns.com/
2600:180c:3001::1
-14


10.027
T
Timeout - The operation has timed out.

• http://u3.verisigndns.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
43.247.170.1
-14


10.016
T
Timeout - The operation has timed out.
Visible Content:

• http://u3.verisigndns.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
2600:180c:3001::1
-14


10.024
T
Timeout - The operation has timed out.
Visible Content:

• https://43.247.170.1/
43.247.170.1
-14


10.020
T
Timeout - The operation has timed out.

• https://[2600:180c:3001:0000:0000:0000:0000:0001]/
2600:180c:3001::1
-14


10.033
T
Timeout - The operation has timed out.

 

7. Comments


1. General Results, most used to calculate the result

Aname "u3.verisigndns.com" is subdomain, 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)
AGood: All ip addresses are public addresses
AGood: Minimal 2 ip addresses per domain name found: u3.verisigndns.com has 2 different ip addresses (authoritative).
AGood: Ipv4 and Ipv6 addresses per domain name found: u3.verisigndns.com has 1 ipv4, 1 ipv6 addresses
AGood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
AGood: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain u3.verisigndns.com, 2 ip addresses.
Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain u3.verisigndns.com, 2 ip addresses.
BNo _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.u3.verisigndns.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

AInfo:: 2 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers.
AInfo:: 2 Queries complete, 2 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
AGood: 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)
AGood (1 - 3.0):: An average of 0.5 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 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.
AGood: Only one SOA.Primary Name Server found.: av1.nstld.com.
AGood: SOA.Primary Name Server included in the delegation set.: av1.nstld.com.
AGood: 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
AGood: All Name Server Domain Names have a Public Suffix.
AGood: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
AGood: All Name Server ip addresses are public.
AGood: Minimal 2 different name servers (public suffix and public ip address) found: 4 different Name Servers found
AGood: 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
AGood: Name servers with different Country locations found: 4 Name Servers, 2 Countries: NL, US
AInfo: 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.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: 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:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 2 good Nameserver
AGood: Nameserver supports Echo Capitalization: 2 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 2 good Nameserver
Nameserver doesn't pass all EDNS-Checks: av1.nstld.com: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
AGood: All SOA have the same Serial Number
Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries.

4. Content- and Performance-critical Checks

http://u3.verisigndns.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 43.247.170.1
-14

Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://u3.verisigndns.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2600:180c:3001::1
-14

Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
AInfo: No img element found, no alt attribute checked
AGood: 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
ADuration: 167490 milliseconds, 167.490 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.DomainTypeNS used
1
com
NS
b.root-servers.net (2001:500:200::b)

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

DomainnameflagNameValue∑ Queries∑ Timeout
u3.verisigndns.com
0

no CAA entry found
1
0
verisigndns.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
verisigndns.com
_bflt06kpbsrunomazny611flfqeuk1y
ok
1
0
u3.verisigndns.com

ok
1
0
_acme-challenge.u3.verisigndns.com

Name Error - The domain name does not exist
1
0
_acme-challenge.u3.verisigndns.com.verisigndns.com

Name Error - The domain name does not exist
1
0
_acme-challenge.u3.verisigndns.com.u3.verisigndns.com

Name Error - The domain name does not exist
1
0

 

16. DomainService - Entries

No DomainServiceEntries entries found

 

 

17. Cipher Suites

No results

 

18. Portchecks

DomainIPPortDescriptionResultAnswer
u3.verisigndns.com
43.247.170.1
21
FTP



u3.verisigndns.com
43.247.170.1
21
FTP



u3.verisigndns.com
43.247.170.1
22
SSH



u3.verisigndns.com
43.247.170.1
22
SSH



u3.verisigndns.com
43.247.170.1
25
SMTP



u3.verisigndns.com
43.247.170.1
25
SMTP



u3.verisigndns.com
43.247.170.1
53
DNS
open


u3.verisigndns.com
43.247.170.1
53
DNS
open


u3.verisigndns.com
43.247.170.1
110
POP3



u3.verisigndns.com
43.247.170.1
110
POP3



u3.verisigndns.com
43.247.170.1
143
IMAP



u3.verisigndns.com
43.247.170.1
143
IMAP



u3.verisigndns.com
43.247.170.1
465
SMTP (encrypted)



u3.verisigndns.com
43.247.170.1
465
SMTP (encrypted)



u3.verisigndns.com
43.247.170.1
587
SMTP (encrypted, submission)



u3.verisigndns.com
43.247.170.1
587
SMTP (encrypted, submission)



u3.verisigndns.com
43.247.170.1
993
IMAP (encrypted)



u3.verisigndns.com
43.247.170.1
993
IMAP (encrypted)



u3.verisigndns.com
43.247.170.1
995
POP3 (encrypted)



u3.verisigndns.com
43.247.170.1
995
POP3 (encrypted)



u3.verisigndns.com
43.247.170.1
1433
MS SQL



u3.verisigndns.com
43.247.170.1
1433
MS SQL



u3.verisigndns.com
43.247.170.1
2082
cPanel (http)



u3.verisigndns.com
43.247.170.1
2082
cPanel (http)



u3.verisigndns.com
43.247.170.1
2083
cPanel (https)



u3.verisigndns.com
43.247.170.1
2083
cPanel (https)



u3.verisigndns.com
43.247.170.1
2086
WHM (http)



u3.verisigndns.com
43.247.170.1
2086
WHM (http)



u3.verisigndns.com
43.247.170.1
2087
WHM (https)



u3.verisigndns.com
43.247.170.1
2087
WHM (https)



u3.verisigndns.com
43.247.170.1
2089
cPanel Licensing



u3.verisigndns.com
43.247.170.1
2089
cPanel Licensing



u3.verisigndns.com
43.247.170.1
2095
cPanel Webmail (http)



u3.verisigndns.com
43.247.170.1
2095
cPanel Webmail (http)



u3.verisigndns.com
43.247.170.1
2096
cPanel Webmail (https)



u3.verisigndns.com
43.247.170.1
2096
cPanel Webmail (https)



u3.verisigndns.com
43.247.170.1
2222
DirectAdmin (http)



u3.verisigndns.com
43.247.170.1
2222
DirectAdmin (http)



u3.verisigndns.com
43.247.170.1
2222
DirectAdmin (https)



u3.verisigndns.com
43.247.170.1
2222
DirectAdmin (https)



u3.verisigndns.com
43.247.170.1
3306
mySql



u3.verisigndns.com
43.247.170.1
3306
mySql



u3.verisigndns.com
43.247.170.1
5224
Plesk Licensing



u3.verisigndns.com
43.247.170.1
5224
Plesk Licensing



u3.verisigndns.com
43.247.170.1
5432
PostgreSQL



u3.verisigndns.com
43.247.170.1
5432
PostgreSQL



u3.verisigndns.com
43.247.170.1
8080
Ookla Speedtest (http)



u3.verisigndns.com
43.247.170.1
8080
Ookla Speedtest (http)



u3.verisigndns.com
43.247.170.1
8080
Ookla Speedtest (https)



u3.verisigndns.com
43.247.170.1
8080
Ookla Speedtest (https)



u3.verisigndns.com
43.247.170.1
8083
VestaCP http



u3.verisigndns.com
43.247.170.1
8083
VestaCP http



u3.verisigndns.com
43.247.170.1
8083
VestaCP https



u3.verisigndns.com
43.247.170.1
8083
VestaCP https



u3.verisigndns.com
43.247.170.1
8443
Plesk Administration (https)



u3.verisigndns.com
43.247.170.1
8443
Plesk Administration (https)



u3.verisigndns.com
43.247.170.1
8447
Plesk Installer + Updates



u3.verisigndns.com
43.247.170.1
8447
Plesk Installer + Updates



u3.verisigndns.com
43.247.170.1
8880
Plesk Administration (http)



u3.verisigndns.com
43.247.170.1
8880
Plesk Administration (http)



u3.verisigndns.com
43.247.170.1
10000
Webmin (http)



u3.verisigndns.com
43.247.170.1
10000
Webmin (http)



u3.verisigndns.com
43.247.170.1
10000
Webmin (https)



u3.verisigndns.com
43.247.170.1
10000
Webmin (https)



u3.verisigndns.com
2600:180c:3001::1
21
FTP



u3.verisigndns.com
2600:180c:3001::1
21
FTP



u3.verisigndns.com
2600:180c:3001::1
22
SSH



u3.verisigndns.com
2600:180c:3001::1
22
SSH



u3.verisigndns.com
2600:180c:3001::1
25
SMTP



u3.verisigndns.com
2600:180c:3001::1
25
SMTP



u3.verisigndns.com
2600:180c:3001::1
53
DNS
open


u3.verisigndns.com
2600:180c:3001::1
53
DNS
open


u3.verisigndns.com
2600:180c:3001::1
110
POP3



u3.verisigndns.com
2600:180c:3001::1
110
POP3



u3.verisigndns.com
2600:180c:3001::1
143
IMAP



u3.verisigndns.com
2600:180c:3001::1
143
IMAP



u3.verisigndns.com
2600:180c:3001::1
465
SMTP (encrypted)



u3.verisigndns.com
2600:180c:3001::1
465
SMTP (encrypted)



u3.verisigndns.com
2600:180c:3001::1
587
SMTP (encrypted, submission)



u3.verisigndns.com
2600:180c:3001::1
587
SMTP (encrypted, submission)



u3.verisigndns.com
2600:180c:3001::1
993
IMAP (encrypted)



u3.verisigndns.com
2600:180c:3001::1
993
IMAP (encrypted)



u3.verisigndns.com
2600:180c:3001::1
995
POP3 (encrypted)



u3.verisigndns.com
2600:180c:3001::1
995
POP3 (encrypted)



u3.verisigndns.com
2600:180c:3001::1
1433
MS SQL



u3.verisigndns.com
2600:180c:3001::1
1433
MS SQL



u3.verisigndns.com
2600:180c:3001::1
2082
cPanel (http)



u3.verisigndns.com
2600:180c:3001::1
2082
cPanel (http)



u3.verisigndns.com
2600:180c:3001::1
2083
cPanel (https)



u3.verisigndns.com
2600:180c:3001::1
2083
cPanel (https)



u3.verisigndns.com
2600:180c:3001::1
2086
WHM (http)



u3.verisigndns.com
2600:180c:3001::1
2086
WHM (http)



u3.verisigndns.com
2600:180c:3001::1
2087
WHM (https)



u3.verisigndns.com
2600:180c:3001::1
2087
WHM (https)



u3.verisigndns.com
2600:180c:3001::1
2089
cPanel Licensing



u3.verisigndns.com
2600:180c:3001::1
2089
cPanel Licensing



u3.verisigndns.com
2600:180c:3001::1
2095
cPanel Webmail (http)



u3.verisigndns.com
2600:180c:3001::1
2095
cPanel Webmail (http)



u3.verisigndns.com
2600:180c:3001::1
2096
cPanel Webmail (https)



u3.verisigndns.com
2600:180c:3001::1
2096
cPanel Webmail (https)



u3.verisigndns.com
2600:180c:3001::1
2222
DirectAdmin (http)



u3.verisigndns.com
2600:180c:3001::1
2222
DirectAdmin (http)



u3.verisigndns.com
2600:180c:3001::1
2222
DirectAdmin (https)



u3.verisigndns.com
2600:180c:3001::1
2222
DirectAdmin (https)



u3.verisigndns.com
2600:180c:3001::1
3306
mySql



u3.verisigndns.com
2600:180c:3001::1
3306
mySql



u3.verisigndns.com
2600:180c:3001::1
5224
Plesk Licensing



u3.verisigndns.com
2600:180c:3001::1
5224
Plesk Licensing



u3.verisigndns.com
2600:180c:3001::1
5432
PostgreSQL



u3.verisigndns.com
2600:180c:3001::1
5432
PostgreSQL



u3.verisigndns.com
2600:180c:3001::1
8080
Ookla Speedtest (http)



u3.verisigndns.com
2600:180c:3001::1
8080
Ookla Speedtest (http)



u3.verisigndns.com
2600:180c:3001::1
8080
Ookla Speedtest (https)



u3.verisigndns.com
2600:180c:3001::1
8080
Ookla Speedtest (https)



u3.verisigndns.com
2600:180c:3001::1
8083
VestaCP http



u3.verisigndns.com
2600:180c:3001::1
8083
VestaCP http



u3.verisigndns.com
2600:180c:3001::1
8083
VestaCP https



u3.verisigndns.com
2600:180c:3001::1
8083
VestaCP https



u3.verisigndns.com
2600:180c:3001::1
8443
Plesk Administration (https)



u3.verisigndns.com
2600:180c:3001::1
8443
Plesk Administration (https)



u3.verisigndns.com
2600:180c:3001::1
8447
Plesk Installer + Updates



u3.verisigndns.com
2600:180c:3001::1
8447
Plesk Installer + Updates



u3.verisigndns.com
2600:180c:3001::1
8880
Plesk Administration (http)



u3.verisigndns.com
2600:180c:3001::1
8880
Plesk Administration (http)



u3.verisigndns.com
2600:180c:3001::1
10000
Webmin (http)



u3.verisigndns.com
2600:180c:3001::1
10000
Webmin (http)



u3.verisigndns.com
2600:180c:3001::1
10000
Webmin (https)



u3.verisigndns.com
2600:180c:3001::1
10000
Webmin (https)



 

 

Permalink: https://check-your-website.server-daten.de/?i=5892e8d6-bc50-40d8-91ca-b7374f4ee64c

 

Last Result: https://check-your-website.server-daten.de/?q=u3.verisigndns.com - 2025-05-09 19:51:08

 

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

 

<a href="https://check-your-website.server-daten.de/?q=u3.verisigndns.com" target="_blank">Check this Site: u3.verisigndns.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=u3.verisigndns.com

 

 

Jürgen Auer • Friedenstr. 37 • 10249 Berlin • +49(0)30 420 200 60 • info@sql-und-xml.de • USt-IdNr.: DE221734518

 

Errors, ideas, questions? Use the Contact form • A project using Server-Daten - Web Database solutions