venmo.com

Checked 22 October 2026, 11:21 UTC · via 8.8.8.8
!Passed with warnings
25 passed 2 warnings 0 failed 4 info

Registration

info

.com generic · MarkMonitor Inc. · expires 2026-12-26

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
MarkMonitor Inc.
Registered
26 December 2008
Last changed
24 November 2025
Expires
26 December 2026
Status
client delete prohibited, client transfer prohibited, client update prohibited, server delete prohibited, server transfer prohibited, server update prohibited
Registry nameservers
ns-1457.awsdns-54.org, ns-1599.awsdns-07.co.uk, ns-304.awsdns-38.com, ns-665.awsdns-19.net
RDAP server
https://rdap.verisign.com/com/v1/

Checks

  • 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 2026-12-26 #3
    The registration is valid until 2026-12-26 (65 days).
  • ✓ Transfer locked #4
    Registry status: client delete prohibited, client transfer prohibited, client update 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.

Delegation

info

ns-1457.awsdns-54.org, ns-1599.awsdns-07.co.uk, ns-304.awsdns-38.com, ns-665.awsdns-19.net

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns-1457.awsdns-54.org, ns-1599.awsdns-07.co.uk, ns-304.awsdns-38.com, ns-665.awsdns-19.net
NS in the zone
ns-1457.awsdns-54.org, ns-1599.awsdns-07.co.uk, ns-304.awsdns-38.com, ns-665.awsdns-19.net
NameserverAddressesNetwork (AS)Glue
ns-1457.awsdns-54.org205.251.197.177 2600:9000:5305:b100::1AS16509 AMAZON-02 - Amazon.com, Inc., US AS16509 AMAZON-02 - Amazon.com, Inc., US-
ns-1599.awsdns-07.co.uk205.251.198.63 2600:9000:5306:3f00::1AS16509 AMAZON-02 - Amazon.com, Inc., US AS16509 AMAZON-02 - Amazon.com, Inc., US-
ns-304.awsdns-38.com205.251.193.48 2600:9000:5301:3000::1AS16509 AMAZON-02 - Amazon.com, Inc., US AS16509 AMAZON-02 - Amazon.com, Inc., US205.251.193.48 2600:9000:5301:3000::1
ns-665.awsdns-19.net205.251.194.153 2600:9000:5302:9900::1AS16509 AMAZON-02 - Amazon.com, Inc., US AS16509 AMAZON-02 - Amazon.com, Inc., US-

Checks

  • ✓ 4 nameservers #6
    Delegated to ns-1457.awsdns-54.org, ns-1599.awsdns-07.co.uk, ns-304.awsdns-38.com, ns-665.awsdns-19.net.
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ No glue needed #8
    All nameservers are outside the zone, so no glue records are needed.
  • ✓ 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 4 IPv4 /24s and 4 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS16509 (AMAZON-02 - Amazon.com, Inc., US): 8 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • ✓ Nameserver names under 4 TLDs #12
    Nameserver names use the TLDs .com, .net, .org, .uk.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

pass

8 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns-1457.awsdns-54.org 205.251.197.177NOERROR, 3 ms, authoritativenoyes / yesrefused-
ns-1457.awsdns-54.org 2600:9000:5305:b100::1NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns-1599.awsdns-07.co.uk 205.251.198.63NOERROR, 9 ms, authoritativenoyes / yesrefused-
ns-1599.awsdns-07.co.uk 2600:9000:5306:3f00::1NOERROR, 9 ms, authoritativenoyes / yesrefused-
ns-304.awsdns-38.com 205.251.193.48NOERROR, 9 ms, authoritativenoyes / yesrefused-
ns-304.awsdns-38.com 2600:9000:5301:3000::1NOERROR, 9 ms, authoritativenoyes / yesrefused-
ns-665.awsdns-19.net 205.251.194.153NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns-665.awsdns-19.net 2600:9000:5302:9900::1NOERROR, 4 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 8 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.
  • ✓ TCP supported #19
    All nameservers answer over TCP.
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 2013011400 · primary ns-1457.awsdns-54.org

Found

Primary (MNAME)
ns-1457.awsdns-54.org
Contact (RNAME)
awsdns-hostmaster.amazon.com
Serial
2013011400
Refresh / retry
7200 s / 900 s
Expire
1209600 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns-1457.awsdns-54.org (205.251.197.177)2013011400
ns-1457.awsdns-54.org (2600:9000:5305:b100::1)2013011400
ns-1599.awsdns-07.co.uk (205.251.198.63)2013011400
ns-1599.awsdns-07.co.uk (2600:9000:5306:3f00::1)2013011400
ns-304.awsdns-38.com (205.251.193.48)2013011400
ns-304.awsdns-38.com (2600:9000:5301:3000::1)2013011400
ns-665.awsdns-19.net (205.251.194.153)2013011400
ns-665.awsdns-19.net (2600:9000:5302:9900::1)2013011400

Checks

  • ✓ Serial 2013011400 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 2h, retry 15m, expire 14d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns-1457.awsdns-54.org is one of the listed nameservers.
  • ✓ Contact awsdns-hostmaster@amazon.com #25
    The SOA RNAME awsdns-hostmaster.amazon.com means awsdns-hostmaster@amazon.com.
  • ✓ Date-based serial #26
    The serial 2013011400 follows the YYYYMMDDnn convention (2013-01-14).

DNSSEC

warn

Not signed

Found

Validated by resolver
no

Checks

  • !
    Not signed
    The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27

Records

warn

26 records at the apex

Found

Read from
205.251.197.177:53
TypeValueTTL
SOAns-1457.awsdns-54.org. awsdns-hostmaster.amazon.com. 2013011400 7200 900 1209600 86400900
NSns-1457.awsdns-54.org.172800
NSns-1599.awsdns-07.co.uk.172800
NSns-304.awsdns-38.com.172800
NSns-665.awsdns-19.net.172800
A52.84.150.5860
A52.84.150.5060
A52.84.150.3460
A52.84.150.3860
MX10 mx1.paypalcorp.com.1800
MX10 mx2.paypalcorp.com.1800
MX20 alt1.aspmx.l.google.com.1800
MX20 aspmx.l.google.com.1800
MX40 aspmx2.googlemail.com.1800
MX50 aspmx3.googlemail.com.1800
TXT"9729qkuraskqi0vr7u6mcf8d49"60
TXT"MS=5AC819E4FED67A8A1BF3CEA57717D6734CBDBFFB"60
TXT"MS=ms65330905"60
TXT"apple-domain-verification=6OGABxXS_kcZlt7_gGCpm3k8ZP8DVA45JigzLiZ4l44"60
TXT"atlassian-domain-verification=Q8BdHlO6NYSN5njfC2rlbPQxksVfADlcxarxq4fesYJErtGKylvfcfyfwrPD/wnv"60
TXT"ghilfs2b8o0k9m6r18jkvvl7t"60
TXT"google-site-verification= jUnvvQ8CzWsJIDQpJn8ticS07DMTfhtEys1fTqdceTg"60
TXT"google-site-verification=IZx3JE7ygg_GZMQt88aoTCi--HWiQgYc2PrVhKgYoZk"60
TXT"google-site-verification=h4sDIUWxgofF1tXZEhGZYwRzoo9BrtW69TXPqTOGfko"60
TXT"status-page-domain-verification=mp810lhmtwdv"60
TXT"v=spf1 ip4:66.211.170.95/32 ip4:66.211.170.86/31 ip4:66.211.170.88/29 ip4:66.211.168.230/31 ip4:74.112.67.243/32 ip4:173.0.84.0/29 ip4:173.0.84.224/28 include:_spf.google.com include:amazonses.com include:sendgrid.net" " include:pp._spf.paypal.com include:mail.zendesk.com include:stspg-customer.com ~all"60

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (1m). Low TTLs are useful just before a planned change.
    #32
  • ✓ 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