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




X

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

Checked:
10.06.2024 21:20:30


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
teamaz.co.in
A
3.33.130.190
Toronto/Ontario/Canada (CA) - Amazon.com, Inc.
Hostname: a2aa9ff50de748dbe.awsglobalaccelerator.com
yes
2
0

A
15.197.148.33
Ashburn/Virginia/United States (US) - Amazon.com, Inc.
Hostname: a2aa9ff50de748dbe.awsglobalaccelerator.com
yes
2
0

AAAA

yes


www.teamaz.co.in
CNAME
teamaz.co.in
yes
1
0

A
3.33.130.190
Toronto/Ontario/Canada (CA) - Amazon.com, Inc.
Hostname: a2aa9ff50de748dbe.awsglobalaccelerator.com
yes



A
15.197.148.33
Ashburn/Virginia/United States (US) - Amazon.com, Inc.
Hostname: a2aa9ff50de748dbe.awsglobalaccelerator.com
yes


*.teamaz.co.in
A
Refused
yes



AAAA
Refused
yes



CNAME
Refused
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



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 5613, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 01.07.2024, 00:00:00 +, Signature-Inception: 10.06.2024, 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: in
in
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 25291, DigestType 2 and Digest KUW2EznfpyIa2C1cbH485OnCUj53VKzIEx0O+UYX4vI=



1 RRSIG RR to validate DS RR found



RRSIG-Owner in., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 23.06.2024, 17:00:00 +, Signature-Inception: 10.06.2024, 16:00:00 +, KeyTag 5613, Signer-Name: (root)



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



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 58671, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner in., Algorithm: 8, 1 Labels, original TTL: 3600 sec, Signature-expiration: 20.06.2024, 01:44:32 +, Signature-Inception: 06.06.2024, 01:25:11 +, KeyTag 25291, Signer-Name: in



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



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

Zone: co.in
co.in
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 53956, DigestType 2 and Digest solL/W7L2uka23JEX+DLhFYUCJwY6kcJpgxLF8EgKsk=



1 RRSIG RR to validate DS RR found



RRSIG-Owner co.in., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 24.06.2024, 03:30:23 +, Signature-Inception: 10.06.2024, 02:37:01 +, KeyTag 58671, Signer-Name: in



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



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 41043, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner co.in., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 20.06.2024, 01:59:58 +, Signature-Inception: 06.06.2024, 01:41:18 +, KeyTag 53956, Signer-Name: co.in



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



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 53956, DigestType 2 and Digest "solL/W7L2uka23JEX+DLhFYUCJwY6kcJpgxLF8EgKsk=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: teamaz.co.in
teamaz.co.in
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 "sav6fo8a6d6nfrervlddspqr2sj3oci4" between the hashed NSEC3-owner "sauhhs9ts8u0ruli8qqa8isfqkam8cqk" and the hashed NextOwner "sb68s6h914o2vmtt2kvh9qd5cku6vftv". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner sauhhs9ts8u0ruli8qqa8isfqkam8cqk.co.in., Algorithm: 8, 3 Labels, original TTL: 900 sec, Signature-expiration: 18.06.2024, 23:17:07 +, Signature-Inception: 04.06.2024, 22:30:20 +, KeyTag 41043, Signer-Name: co.in



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "2gdr1hu1fvrntiasqa6g3amn55gmi9o3" as Owner. That's the Hash of "co.in" with the NextHashedOwnerName "2gg50cv27s0g2f5pitndckms1o0hjh15". So that domain name is the Closest Encloser of "teamaz.co.in". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS, CDNSKEY Validated: RRSIG-Owner 2gdr1hu1fvrntiasqa6g3amn55gmi9o3.co.in., Algorithm: 8, 3 Labels, original TTL: 900 sec, Signature-expiration: 18.06.2024, 23:21:56 +, Signature-Inception: 04.06.2024, 22:37:16 +, KeyTag 41043, Signer-Name: co.in



0 DNSKEY RR found




Zone: www.teamaz.co.in
www.teamaz.co.in
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
teamaz.co.in
  ns1-38.azure-dns.com
150.171.10.38
Cleveland/Ohio/United States (US) - Microsoft Corporation


 
2603:1061:0:10::26
Toronto/Ontario/Canada (CA) - Microsoft Corporation


  ns2-38.azure-dns.net
150.171.16.38
Québec/Canada (CA) - Microsoft Corporation


 
2620:1ec:8ec:10::26
Redmond/Washington/United States (US) - Microsoft Corporation


  ns25.domaincontrol.com / hex:0D 70 30 37
97.74.102.13
Tempe/Arizona/United States (US) - Host Europe GmbH


 
2603:5:2161::d
Chicago/Illinois/United States (US) - Host Europe GmbH


  ns26.domaincontrol.com / hex:0D 70 31 30
173.201.70.13
Tempe/Arizona/United States (US) - Host Europe GmbH


 
2603:5:2261::d
Chicago/Illinois/United States (US) - Host Europe GmbH


  ns3-38.azure-dns.org
13.107.222.38
Québec/Canada (CA) - Xerox Corporation


 
2a01:111:4000:10::26
Cheyenne/Wyoming/United States (US) - Microsoft


  ns4-38.azure-dns.info
13.107.206.38
Ashburn/Virginia/United States (US) - Xerox Corporation


 
2620:1ec:bda:10::26
Redmond/Washington/United States (US) - Microsoft Corporation

co.in
  ns1.registry.in / dns3.defra1
37.209.192.12
Melbourne/Victoria/Australia (AU) - NeuStar, Inc.


 
2001:dcd:1::12
Melbourne/Victoria/Australia (AU) - NeuStar, Inc.


  ns2.registry.in / dns1.defra1
37.209.194.12
Sydney/New South Wales/Australia (AU) - NeuStar, Inc.


 
2001:dcd:2::12
Melbourne/Victoria/Australia (AU) - NeuStar, Inc.


  ns3.registry.in / dns3.defra1
37.209.196.12
Sydney/New South Wales/Australia (AU) - NeuStar, Inc.


 
2001:dcd:3::12
Melbourne/Victoria/Australia (AU) - NeuStar, Inc.


  ns4.registry.in / dns1.defra1
37.209.198.12
Talladega/Alabama/United States (US) - NeuStar, Inc.


 
2001:dcd:4::12
Melbourne/Victoria/Australia (AU) - NeuStar, Inc.


  ns5.registry.in / TLD_Host2.Frankfurt_Node1
156.154.100.20
New York/United States (US) - NeuStar, Inc.


 
2001:502:2eda::20
Herndon/Virginia/United States (US) - NeuStar, Inc.


  ns6.registry.in / TLD_Host1.Frankfurt_Node1
156.154.101.20
New York/United States (US) - NeuStar, Inc.


 
2001:502:ad09::20
Herndon/Virginia/United States (US) - NeuStar, Inc.

in
  ns1.registry.in / dns2.defra1


  ns2.registry.in / dns4.defra1


  ns3.registry.in / dns2.defra1


  ns4.registry.in / dns1.defra1


  ns5.registry.in / TLD_Host2.Frankfurt_Node1


  ns6.registry.in / TLD_Host1.Frankfurt_Node1


4. SOA-Entries


Domain:in
Zone-Name:in
Primary:ns1.registry.in
Mail:dns.registry.in
Serial:1718046810
Refresh:1800
Retry:300
Expire:1814400
TTL:1800
num Entries:6


Domain:co.in
Zone-Name:co.in
Primary:ns1.registry.in
Mail:dns.registry.in
Serial:1718046818
Refresh:1800
Retry:300
Expire:1814400
TTL:1800
num Entries:12


Domain:teamaz.co.in
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:8


Domain:teamaz.co.in
Zone-Name:teamaz.co.in
Primary:ns25.domaincontrol.com
Mail:dns.jomax.net
Serial:2024061013
Refresh:28800
Retry:7200
Expire:604800
TTL:600
num Entries:4


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://teamaz.co.in/
3.33.130.190
200

Html is minified: 278.05 %
0.217
H
Server: openresty
Date: Mon, 10 Jun 2024 19:21:29 GMT
Connection: close
Content-Type: text/html
Content-Length: 114

• http://teamaz.co.in/
15.197.148.33
200

Html is minified: 278.05 %
0.203
H
Server: openresty
Date: Mon, 10 Jun 2024 19:21:29 GMT
Connection: close
Content-Type: text/html
Content-Length: 114

• http://www.teamaz.co.in/
3.33.130.190
200

Html is minified: 278.05 %
0.203
H
Server: openresty
Date: Mon, 10 Jun 2024 19:21:30 GMT
Connection: close
Content-Type: text/html
Content-Length: 114

• http://www.teamaz.co.in/
15.197.148.33
200

Html is minified: 278.05 %
0.216
H
Server: openresty
Date: Mon, 10 Jun 2024 19:21:30 GMT
Connection: close
Content-Type: text/html
Content-Length: 114

• https://teamaz.co.in/
3.33.130.190
-16

0.237
P
UnknownError - The SSL connection could not be established, see inner exception. - Authentication failed because the remote party sent a TLS alert: '112' (FF: SSL_ERROR_UNRECOGNIZED_NAME_ALERT).

• https://teamaz.co.in/
15.197.148.33
-16

1.240
P
UnknownError - The SSL connection could not be established, see inner exception. - Authentication failed because the remote party sent a TLS alert: '112' (FF: SSL_ERROR_UNRECOGNIZED_NAME_ALERT).

• https://www.teamaz.co.in/
3.33.130.190
-16

0.223
P
UnknownError - The SSL connection could not be established, see inner exception. - Authentication failed because the remote party sent a TLS alert: '112' (FF: SSL_ERROR_UNRECOGNIZED_NAME_ALERT).

• https://www.teamaz.co.in/
15.197.148.33
-16

1.260
P
UnknownError - The SSL connection could not be established, see inner exception. - Authentication failed because the remote party sent a TLS alert: '112' (FF: SSL_ERROR_UNRECOGNIZED_NAME_ALERT).

• http://teamaz.co.in/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
3.33.130.190
-16

1.786
W
UnknownError - An error occurred while sending the request.
Visible Content:

• http://teamaz.co.in/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
15.197.148.33
-16

1.823
W
UnknownError - An error occurred while sending the request.
Visible Content:

• http://www.teamaz.co.in/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
3.33.130.190
-16

0.793
W
UnknownError - An error occurred while sending the request.
Visible Content:

• http://www.teamaz.co.in/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
15.197.148.33
-16

0.813
W
UnknownError - An error occurred while sending the request.
Visible Content:

• https://3.33.130.190/
3.33.130.190
-16

0.223
P
UnknownError - The SSL connection could not be established, see inner exception. - Received an unexpected EOF or 0 bytes from the transport stream (FF: PR_END_OF_FILE_ERROR)

• https://15.197.148.33/
15.197.148.33
-16

0.203
P
UnknownError - The SSL connection could not be established, see inner exception. - Received an unexpected EOF or 0 bytes from the transport stream (FF: PR_END_OF_FILE_ERROR)

7. Comments


1. General Results, most used to calculate the result

Aname "teamaz.co.in" is domain, public suffix is ".co.in", top-level-domain is ".in", top-level-domain-type is "country-code", Country is India, tld-manager is "National Internet Exchange of India", num .in-domains preloaded: 1081 (complete: 245733)
AGood: All ip addresses are public addresses
AGood: Minimal 2 ip addresses per domain name found: teamaz.co.in has 2 different ip addresses (authoritative).
AGood: Minimal 2 ip addresses per domain name found: www.teamaz.co.in has 2 different ip addresses (authoritative).
Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: teamaz.co.in has no ipv6 address.
Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: www.teamaz.co.in has no ipv6 address.
AGood: No asked Authoritative Name Server had a timeout
AGood: No cookie sent via http.
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: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):0 complete Content-Type - header (4 urls)
http://teamaz.co.in/ 3.33.130.190


Url with incomplete Content-Type - header - missing charset
http://teamaz.co.in/ 15.197.148.33


Url with incomplete Content-Type - header - missing charset
http://www.teamaz.co.in/ 3.33.130.190


Url with incomplete Content-Type - header - missing charset
http://www.teamaz.co.in/ 15.197.148.33


Url with incomplete Content-Type - header - missing charset
HFatal error: No https - result with http-status 200, no encryption
HFatal error: http result with http-status 200, no encryption. Add a redirect http ⇒ https, so every connection is secure. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop.
XFatal error: Nameserver doesn't support TCP connection: ns1-38.azure-dns.com / 150.171.10.38: Refused
XFatal error: Nameserver doesn't support TCP connection: ns1-38.azure-dns.com / 2603:1061:0:10::26: Refused
XFatal error: Nameserver doesn't support TCP connection: ns2-38.azure-dns.net / 150.171.16.38: Refused
XFatal error: Nameserver doesn't support TCP connection: ns2-38.azure-dns.net / 2620:1ec:8ec:10::26: Refused
XFatal error: Nameserver doesn't support TCP connection: ns3-38.azure-dns.org / 13.107.222.38: Refused
XFatal error: Nameserver doesn't support TCP connection: ns3-38.azure-dns.org / 2a01:111:4000:10::26: Refused
XFatal error: Nameserver doesn't support TCP connection: ns4-38.azure-dns.info / 13.107.206.38: Refused
XFatal error: Nameserver doesn't support TCP connection: ns4-38.azure-dns.info / 2620:1ec:bda:10::26: Refused
AGood: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain teamaz.co.in, 2 ip addresses.
AGood: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain www.teamaz.co.in, 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 teamaz.co.in, 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 www.teamaz.co.in, 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.teamaz.co.in

2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05)

U

No https result with http status 2** or 4** (standard-check) found, no header checked.

3. DNS- and NameServer - Checks

AInfo:: 43 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 6 Name Servers.
AInfo:: 43 Queries complete, 43 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
Ok (4 - 8):: An average of 7.2 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 6 different Name Servers found: ns1-38.azure-dns.com, ns2-38.azure-dns.net, ns25.domaincontrol.com, ns26.domaincontrol.com, ns3-38.azure-dns.org, ns4-38.azure-dns.info, 2 Name Servers included in Delegation: ns25.domaincontrol.com, ns26.domaincontrol.com, 6 Name Servers included in 2 Zone definitions: ns1-38.azure-dns.com, ns2-38.azure-dns.net, ns25.domaincontrol.com, ns26.domaincontrol.com, ns3-38.azure-dns.org, ns4-38.azure-dns.info, 1 Name Servers listed in SOA.Primary: ns25.domaincontrol.com.
AGood: Only one SOA.Primary Name Server found.: ns25.domaincontrol.com.
AGood: SOA.Primary Name Server included in the delegation set.: ns25.domaincontrol.com.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns25.domaincontrol.com (97.74.102.13): Delegation: ns25.domaincontrol.com, ns26.domaincontrol.com, Zone: ns1-38.azure-dns.com, ns2-38.azure-dns.net, ns25.domaincontrol.com, ns26.domaincontrol.com, ns3-38.azure-dns.org, ns4-38.azure-dns.info. Name Servers defined in Zone, missing in Delegation: ns1-38.azure-dns.com, ns2-38.azure-dns.net, ns3-38.azure-dns.org, ns4-38.azure-dns.info.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns25.domaincontrol.com (2603:5:2161::d): Delegation: ns25.domaincontrol.com, ns26.domaincontrol.com, Zone: ns1-38.azure-dns.com, ns2-38.azure-dns.net, ns25.domaincontrol.com, ns26.domaincontrol.com, ns3-38.azure-dns.org, ns4-38.azure-dns.info. Name Servers defined in Zone, missing in Delegation: ns1-38.azure-dns.com, ns2-38.azure-dns.net, ns3-38.azure-dns.org, ns4-38.azure-dns.info.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns26.domaincontrol.com (173.201.70.13): Delegation: ns25.domaincontrol.com, ns26.domaincontrol.com, Zone: ns1-38.azure-dns.com, ns2-38.azure-dns.net, ns25.domaincontrol.com, ns26.domaincontrol.com, ns3-38.azure-dns.org, ns4-38.azure-dns.info. Name Servers defined in Zone, missing in Delegation: ns1-38.azure-dns.com, ns2-38.azure-dns.net, ns3-38.azure-dns.org, ns4-38.azure-dns.info.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns26.domaincontrol.com (2603:5:2261::d): Delegation: ns25.domaincontrol.com, ns26.domaincontrol.com, Zone: ns1-38.azure-dns.com, ns2-38.azure-dns.net, ns25.domaincontrol.com, ns26.domaincontrol.com, ns3-38.azure-dns.org, ns4-38.azure-dns.info. Name Servers defined in Zone, missing in Delegation: ns1-38.azure-dns.com, ns2-38.azure-dns.net, ns3-38.azure-dns.org, ns4-38.azure-dns.info.
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: 6 different Name Servers found
AGood: All name servers have ipv4- and ipv6-addresses.: 6 different Name Servers found
AGood: Name servers with different Top Level Domains / Public Suffix List entries found: 6 Name Servers, 4 Top Level Domains: com, org, net, info
AGood: Name Servers with different domain names found.: 5 different Domains found
AGood: Name servers with different Country locations found: 6 Name Servers, 2 Countries: CA, US
AInfo: Ipv4-Subnet-list: 6 Name Servers, 4 different subnets (first Byte): 13., 150., 173., 97., 4 different subnets (first two Bytes): 13.107., 150.171., 173.201., 97.74., 6 different subnets (first three Bytes): 13.107.206., 13.107.222., 150.171.10., 150.171.16., 173.201.70., 97.74.102.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 6 Name Servers with IPv6, 3 different subnets (first block): 2603:, 2620:, 2a01:, 4 different subnets (first two blocks): 2603:0005:, 2603:1061:, 2620:01ec:, 2a01:0111:, 6 different subnets (first three blocks): 2603:0005:2161:, 2603:0005:2261:, 2603:1061:0000:, 2620:01ec:08ec:, 2620:01ec:0bda:, 2a01:0111:4000:, 6 different subnets (first four blocks): 2603:0005:2161:0000:, 2603:0005:2261:0000:, 2603:1061:0000:0010:, 2620:01ec:08ec:0010:, 2620:01ec:0bda:0010:, 2a01:0111:4000:0010:
AGood: Name Server IPv6 addresses from different subnets found.
AInfo: Nameserver mit different domain names found. May be a problem with DNS-Updates
AGood: Nameserver supports Echo Capitalization: 12 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 12 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 4 good Nameserver
Nameserver doesn't pass all EDNS-Checks: ns1-38.azure-dns.com / 150.171.10.38: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns1-38.azure-dns.com / 2603:1061:0:10::26: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns2-38.azure-dns.net / 150.171.16.38: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns2-38.azure-dns.net / 2620:1ec:8ec:10::26: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns3-38.azure-dns.org / 13.107.222.38: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns3-38.azure-dns.org / 2a01:111:4000:10::26: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns4-38.azure-dns.info / 13.107.206.38: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns4-38.azure-dns.info / 2620:1ec:bda:10::26: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok.
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://teamaz.co.in/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 3.33.130.190
-16

Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. 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://teamaz.co.in/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 15.197.148.33
-16

Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. 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://www.teamaz.co.in/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 3.33.130.190
-16

Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. 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://www.teamaz.co.in/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 15.197.148.33
-16

Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. 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: 276023 milliseconds, 276.023 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

Issuerlast 7 daysactivenum Certs
CN=GeoTrust Global TLS RSA4096 SHA256 2022 CA1, O="DigiCert, Inc.", C=US
0
0
1

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
10674251610
precert
CN=GeoTrust Global TLS RSA4096 SHA256 2022 CA1, O="DigiCert, Inc.", C=US
2023-10-08 22:00:00
2024-04-09 21:59:59
teamaz.co.in
1 entries



11. Html-Content - Entries

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


12. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns1-38.azure-dns.com, ns2-38.azure-dns.net, ns25.domaincontrol.com, ns26.domaincontrol.com, ns3-38.azure-dns.org, ns4-38.azure-dns.info

QNr.DomainTypeNS used
1
com
NS
e.root-servers.net (2001:500:a8::e)

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
ns1-38.azure-dns.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns1-01.azure-dns.com, ns1-02.azure-dns.com, ns1-03.azure-dns.com, ns1-04.azure-dns.com

Answer: ns1-01.azure-dns.com
13.107.236.1, 2603:1061:0:700::1

Answer: ns1-02.azure-dns.com
13.107.236.2, 2603:1061:0:700::2

Answer: ns1-03.azure-dns.com
13.107.236.3, 2603:1061:0:700::3

Answer: ns1-04.azure-dns.com
13.107.236.4, 2603:1061:0:700::4
3
net
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
4
ns2-38.azure-dns.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns2-01.azure-dns.net, ns2-02.azure-dns.net, ns2-03.azure-dns.net, ns2-04.azure-dns.net

Answer: ns2-01.azure-dns.net
150.171.21.1, 2620:1ec:8ec:700::1

Answer: ns2-02.azure-dns.net
150.171.21.2, 2620:1ec:8ec:700::2

Answer: ns2-03.azure-dns.net
150.171.21.3, 2620:1ec:8ec:700::3

Answer: ns2-04.azure-dns.net
150.171.21.4, 2620:1ec:8ec:700::4
5
ns25.domaincontrol.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-245.akam.net, a11-64.akam.net, a20-65.akam.net, a6-66.akam.net, a8-67.akam.net, a9-67.akam.net, ans01.domaincontrol.com, ans02.domaincontrol.com

Answer: ans01.domaincontrol.com
2603:5:2111::23, 97.74.97.35

Answer: ans02.domaincontrol.com
173.201.65.35, 2603:5:2211::23
6
ns26.domaincontrol.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-245.akam.net, a11-64.akam.net, a20-65.akam.net, a6-66.akam.net, a8-67.akam.net, a9-67.akam.net, ans01.domaincontrol.com, ans02.domaincontrol.com

Answer: ans01.domaincontrol.com
2603:5:2111::23, 97.74.97.35

Answer: ans02.domaincontrol.com
173.201.65.35, 2603:5:2211::23
7
org
NS
c.root-servers.net (2001:500:2::c)

Answer: a0.org.afilias-nst.info, a2.org.afilias-nst.info, b0.org.afilias-nst.org, b2.org.afilias-nst.org, c0.org.afilias-nst.info, d0.org.afilias-nst.org
8
ns3-38.azure-dns.org
NS
a0.org.afilias-nst.info (2001:500:e::1)

Answer: ns3-01.azure-dns.org, ns3-02.azure-dns.org, ns3-03.azure-dns.org, ns3-04.azure-dns.org

Answer: ns3-01.azure-dns.org
204.14.183.1, 2a01:111:4000:700::1

Answer: ns3-02.azure-dns.org
204.14.183.2, 2a01:111:4000:700::2

Answer: ns3-03.azure-dns.org
204.14.183.3, 2a01:111:4000:700::3

Answer: ns3-04.azure-dns.org
204.14.183.4, 2a01:111:4000:700::4
9
info
NS
k.root-servers.net (2001:7fd::1)

Answer: a0.info.afilias-nst.info, a2.info.afilias-nst.info, b0.info.afilias-nst.org, b2.info.afilias-nst.org, c0.info.afilias-nst.info, d0.info.afilias-nst.org
10
ns4-38.azure-dns.info
NS
a0.info.afilias-nst.info (2001:500:19::1)

Answer: ns4-01.azure-dns.info, ns4-02.azure-dns.info, ns4-03.azure-dns.info, ns4-04.azure-dns.info

Answer: ns4-01.azure-dns.info
208.84.5.1, 2620:1ec:bda:700::1

Answer: ns4-02.azure-dns.info
208.84.5.2, 2620:1ec:bda:700::2

Answer: ns4-03.azure-dns.info
208.84.5.3, 2620:1ec:bda:700::3

Answer: ns4-04.azure-dns.info
208.84.5.4, 2620:1ec:bda:700::4
11
a1-245.akam.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a4-67.akam.net, a6-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
2600:1480:1::43, 84.53.139.67

Answer: a12-67.akam.net
184.26.160.67, 2600:1480:f000::43

Answer: a18-67.akam.net
2600:1480:4800::43, 95.101.36.67

Answer: a22-67.akam.net
23.211.61.67, 2600:1480:7800::43

Answer: a28-67.akam.net
2600:1480:d800::43, 95.100.173.67

Answer: a4-67.akam.net
2600:1480:9000::43, 72.246.46.67
12
a11-64.akam.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a4-67.akam.net, a6-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
2600:1480:1::43, 84.53.139.67

Answer: a12-67.akam.net
184.26.160.67, 2600:1480:f000::43

Answer: a18-67.akam.net
2600:1480:4800::43, 95.101.36.67

Answer: a22-67.akam.net
23.211.61.67, 2600:1480:7800::43

Answer: a28-67.akam.net
2600:1480:d800::43, 95.100.173.67

Answer: a4-67.akam.net
2600:1480:9000::43, 72.246.46.67
13
a20-65.akam.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a4-67.akam.net, a6-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
2600:1480:1::43, 84.53.139.67

Answer: a12-67.akam.net
184.26.160.67, 2600:1480:f000::43

Answer: a18-67.akam.net
2600:1480:4800::43, 95.101.36.67

Answer: a22-67.akam.net
23.211.61.67, 2600:1480:7800::43

Answer: a28-67.akam.net
2600:1480:d800::43, 95.100.173.67

Answer: a4-67.akam.net
2600:1480:9000::43, 72.246.46.67
14
a6-66.akam.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a4-67.akam.net, a6-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
2600:1480:1::43, 84.53.139.67

Answer: a12-67.akam.net
184.26.160.67, 2600:1480:f000::43

Answer: a18-67.akam.net
2600:1480:4800::43, 95.101.36.67

Answer: a22-67.akam.net
23.211.61.67, 2600:1480:7800::43

Answer: a28-67.akam.net
2600:1480:d800::43, 95.100.173.67

Answer: a4-67.akam.net
2600:1480:9000::43, 72.246.46.67
15
a8-67.akam.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a4-67.akam.net, a6-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
2600:1480:1::43, 84.53.139.67

Answer: a12-67.akam.net
184.26.160.67, 2600:1480:f000::43

Answer: a18-67.akam.net
2600:1480:4800::43, 95.101.36.67

Answer: a22-67.akam.net
23.211.61.67, 2600:1480:7800::43

Answer: a28-67.akam.net
2600:1480:d800::43, 95.100.173.67

Answer: a4-67.akam.net
2600:1480:9000::43, 72.246.46.67
16
a9-67.akam.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a4-67.akam.net, a6-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
2600:1480:1::43, 84.53.139.67

Answer: a12-67.akam.net
184.26.160.67, 2600:1480:f000::43

Answer: a18-67.akam.net
2600:1480:4800::43, 95.101.36.67

Answer: a22-67.akam.net
23.211.61.67, 2600:1480:7800::43

Answer: a28-67.akam.net
2600:1480:d800::43, 95.100.173.67

Answer: a4-67.akam.net
2600:1480:9000::43, 72.246.46.67
17
a6-67.akam.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a4-67.akam.net, a6-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
2600:1480:1::43, 84.53.139.67

Answer: a12-67.akam.net
184.26.160.67, 2600:1480:f000::43

Answer: a18-67.akam.net
2600:1480:4800::43, 95.101.36.67

Answer: a22-67.akam.net
23.211.61.67, 2600:1480:7800::43

Answer: a28-67.akam.net
2600:1480:d800::43, 95.100.173.67

Answer: a4-67.akam.net
2600:1480:9000::43, 72.246.46.67
18
a1-245.akam.net: 193.108.91.245
A
a1-67.akam.net (2600:1401:2::43)
19
a1-245.akam.net: 2600:1401:2::f5
AAAA
a1-67.akam.net (2600:1401:2::43)
20
a11-64.akam.net: 84.53.139.64
A
a1-67.akam.net (2600:1401:2::43)
21
a11-64.akam.net: 2600:1480:1::40
AAAA
a1-67.akam.net (2600:1401:2::43)
22
a20-65.akam.net: 95.100.175.65
A
a1-67.akam.net (2600:1401:2::43)
23
a20-65.akam.net: 2a02:26f0:67::41
AAAA
a1-67.akam.net (2600:1401:2::43)
24
a6-66.akam.net: 23.211.133.66
A
a1-67.akam.net (2600:1401:2::43)
25
a6-66.akam.net: 2600:1401:1::42
AAAA
a1-67.akam.net (2600:1401:2::43)
26
a8-67.akam.net: 2.16.40.67
A
a1-67.akam.net (2600:1401:2::43)
27
a8-67.akam.net: 2600:1403:a::43
AAAA
a1-67.akam.net (2600:1401:2::43)
28
a9-67.akam.net: 184.85.248.67
A
a1-67.akam.net (2600:1401:2::43)
29
a9-67.akam.net: 2a02:26f0:117::43
AAAA
a1-67.akam.net (2600:1401:2::43)
30
a6-67.akam.net: 23.211.133.67
A
a1-67.akam.net (2600:1401:2::43)
31
a6-67.akam.net: 2600:1401:1::43
AAAA
a1-67.akam.net (2600:1401:2::43)
32
ns1-38.azure-dns.com: 150.171.10.38
A
ns1-01.azure-dns.com (2603:1061:0:700::1)
33
ns1-38.azure-dns.com: 2603:1061:0:10::26
AAAA
ns1-01.azure-dns.com (2603:1061:0:700::1)
34
ns2-38.azure-dns.net: 150.171.16.38
A
ns2-01.azure-dns.net (2620:1ec:8ec:700::1)
35
ns2-38.azure-dns.net: 2620:1ec:8ec:10::26
AAAA
ns2-01.azure-dns.net (2620:1ec:8ec:700::1)
36
ns25.domaincontrol.com: 97.74.102.13
A
a1-245.akam.net (2600:1401:2::f5)
37
ns25.domaincontrol.com: 2603:5:2161::d
AAAA
a1-245.akam.net (2600:1401:2::f5)
38
ns26.domaincontrol.com: 173.201.70.13
A
a1-245.akam.net (2600:1401:2::f5)
39
ns26.domaincontrol.com: 2603:5:2261::d
AAAA
a1-245.akam.net (2600:1401:2::f5)
40
ns3-38.azure-dns.org: 13.107.222.38
A
ns3-01.azure-dns.org (2a01:111:4000:700::1)
41
ns3-38.azure-dns.org: 2a01:111:4000:10::26
AAAA
ns3-01.azure-dns.org (2a01:111:4000:700::1)
42
ns4-38.azure-dns.info: 13.107.206.38
A
ns4-01.azure-dns.info (2620:1ec:bda:700::1)
43
ns4-38.azure-dns.info: 2620:1ec:bda:10::26
AAAA
ns4-01.azure-dns.info (2620:1ec:bda:700::1)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.teamaz.co.in



1
0
teamaz.co.in
0

no CAA entry found
1
0
co.in
0

no CAA entry found
1
0
in
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
teamaz.co.in
MS=ms37034614
ok
1
0
www.teamaz.co.in
MS=ms37034614
ok
1
0
_acme-challenge.teamaz.co.in

Name Error - The domain name does not exist
1
0
_acme-challenge.www.teamaz.co.in

Name Error - The domain name does not exist
1
0
_acme-challenge.teamaz.co.in.teamaz.co.in

Name Error - The domain name does not exist
1
0
_acme-challenge.www.teamaz.co.in.teamaz.co.in

Name Error - The domain name does not exist
1
0
_acme-challenge.www.teamaz.co.in.www.teamaz.co.in

Name Error - The domain name does not exist
1
0


15. DomainService - Entries

TypeDomainPrefValueDNS-errornum AnswersStatusDescription
MX

teamaz.co.in
32767
ms37034614.msv1.invalid
01ok

CNAME


-30ok



16. Cipher Suites

No results


17. Portchecks

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



Permalink: https://check-your-website.server-daten.de/?i=518e402d-3127-420f-b3e2-98fe6936ff0d


Last Result: https://check-your-website.server-daten.de/?q=teamaz.co.in - 2024-06-10 21:20:30


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

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

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