Domain report: 50megs.com

Registration

info

.com generic · CSC Corporate Domains, Inc. · expires 2027-06-07

TLD: .com (generic)
ICANN policies apply: yes
Registrar: CSC Corporate Domains, Inc.
Registered: 7 June 1999
Last changed: 3 June 2026
Expires: 7 June 2027
Status: client transfer prohibited, server delete prohibited, server transfer prohibited, server update prohibited
Registry nameservers: ns1.50megs.com, ns2.50megs.com
RDAP server: https://rdap.verisign.com/com/v1/

i

.com is a generic TLD (gTLD)

Generic TLD under an ICANN registry agreement: ICANN-accredited registrars, UDRP and RDAP apply.

#1
✓ TLD delegated and signed #2

.com is delegated in the root zone and DNSSEC-signed.
✓ Expires on 2027-06-07 #3

The registration is valid until 2027-06-07 (227 days).
✓ Transfer locked #4

Registry status: client transfer prohibited, server delete prohibited, server transfer prohibited, server update prohibited.
✓ Registry and delegation match #5

The nameservers registered at the registry are the ones published in DNS.

warn

ns1.50megs.com, ns2.50megs.com

Nameserver	Addresses	Network (AS)	Glue
ns1.50megs.com (parent only)	64.136.25.254	AS13446 AS-NETZERO - Netzero,INC., US	64.136.25.254
ns1.freeservers.com (zone only)	64.136.25.253	AS13446 AS-NETZERO - Netzero,INC., US	-
ns2.50megs.com (parent only)	64.136.44.123	AS13446 AS-NETZERO - Netzero,INC., US	64.136.44.123
ns2.freeservers.com (zone only)	64.136.44.123	AS13446 AS-NETZERO - Netzero,INC., US	-

i

2 nameservers

Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.50megs.com, ns2.50megs.com.

#6
!

NS sets differ

The nameservers at the parent and in the zone should be the same. Only at the parent: ns1.50megs.com, ns2.50megs.com; only in the zone: ns1.freeservers.com, ns2.freeservers.com. ns1.50megs.com, ns1.freeservers.com, ns2.50megs.com, ns2.freeservers.com report NS ns1.freeservers.com ns2.freeservers.com.

#7
✓ Glue present and correct #8

Glue is published for the nameservers inside the zone: ns1.50megs.com, ns2.50megs.com.
✓ All names resolve #9

Every nameserver name has an address and is not an alias.
✓ Nameservers in different networks #10

The nameservers are spread over 2 IPv4 /24s and 0 IPv6 /48s.
i

All nameservers in one AS

All nameserver addresses are announced by one network operator (AS13446 (AS-NETZERO - Netzero,INC., US): 4 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.

#11
i

All nameserver names under .com

All nameserver names are under one TLD, so a problem with that TLD also makes the nameservers unreachable. Some operators use names under two TLDs for extra resilience.

#12
!

No IPv6

None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.

#13

fail

4 of 4 addresses answer authoritatively

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
ns1.50megs.com 64.136.25.254	NOERROR, 145 ms, authoritative	no	no / no	refused	-
ns1.freeservers.com 64.136.25.253	NOERROR, 142 ms, authoritative	no	no / no	refused	-
ns2.50megs.com 64.136.44.123	NOERROR, 105 ms, authoritative	no	no / no	refused	-
ns2.freeservers.com 64.136.44.123	NOERROR, 105 ms, authoritative	no	no / no	refused	-

✓ All respond #14

All 4 nameserver addresses answered.
✓ All authoritative #15

Every responding nameserver answers authoritatively for the zone.
✓ No recursion #16

The nameservers do not answer recursive queries for other domains.
✓ No version disclosed #17

The nameservers don't reveal their software version.
✓ Zone transfers refused #18

No nameserver allows a zone transfer to the public.
✗

No DNS over TCP

DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: ns1.50megs.com (64.136.25.254): dial tcp 64.136.25.254:53: connect: connection refused; ns1.freeservers.com (64.136.25.253): dial tcp 64.136.25.253:53: connect: connection refused; ns2.50megs.com (64.136.44.123): dial tcp 64.136.44.123:53: connect: connection refused; ns2.freeservers.com (64.136.44.123): dial tcp 64.136.44.123:53: connect: connection refused.

#19
!

No EDNS

These nameservers don't support EDNS(0), needed for DNSSEC and answers larger than 512 bytes: ns1.50megs.com (64.136.25.254), ns1.freeservers.com (64.136.25.253), ns2.50megs.com (64.136.44.123), ns2.freeservers.com (64.136.44.123).

#20
✓ Public addresses #21

All nameserver addresses are publicly routable.

warn

serial 1791756764 · primary ns1.global-servers.com

✓ Serial 1791756764 everywhere #22

All nameservers serve the same version of the zone.
!

Unusual SOA timers

refresh 5m is outside 20m–1d; retry 5m should be shorter than refresh 5m. Current values: refresh 5m, retry 5m, expire 7d, negative TTL 5m.

#23
i

Hidden master

The primary nameserver ns1.global-servers.com is not listed as a nameserver: a hidden master that only feeds the public secondaries. That is a common setup; make sure it is not reachable for zone transfers from outside.

#24
✓ Contact dns@50megs.com #25

The SOA RNAME dns.50megs.com means dns@50megs.com.
✓ Timestamp serial #26

The serial 1791756764 is a Unix timestamp (2026-10-11 22:12 UTC).

warn

Not signed

info

6 records at the apex

Type	Value	TTL
SOA	ns1.global-servers.com. dns.50megs.com. 1791756764 300 300 604800 300	300
NS	ns1.freeservers.com.	300
NS	ns2.freeservers.com.	300
A	64.136.20.69	300
MX	10 mx-ws.dca.untd.com.	300
MX	10 mx-ws.vgs.untd.com.	300

✓ TTLs within range #32

TTLs: A 5m, MX 5m, NS 5m. The NS TTL at the parent is 2d and in the zone 5m; resolvers may use either.
✓ No CNAME at the apex #33

The zone apex has no CNAME record.
i

Wildcard record

A random name under the zone resolves, so there is a wildcard (*) record. Typos and non-existent hosts resolve too, which can confuse mail and certificate checks.

#34
i

No CAA records

Without CAA records any certificate authority may issue certificates for this domain. A CAA record limits issuance to the CAs you use.

#35