AboutUs hasn't finished checking this site yet — the live checks below are current; more details appear as we crawl it.
pullcm.com
Verifying against the live site and live WHOIS/DNS…
Common questions
Is pullcm.com legit or a scam?
pullcm.com was registered Jun 30, 2020 (6 years old), per public registration records. AboutUs doesn't label sites "legit" or "a scam": this page lists the dated registration, DNS, HTTPS, mail-authentication and safety checks we could verify, each with its source, so you can decide for yourself.
Who owns pullcm.com?
Nobody has completed AboutUs's owner verification for pullcm.com. That's true of most sites here — it isn't itself a warning sign.
When was pullcm.com registered?
pullcm.com's registration dates to Jun 30, 2020 (6 years old), per public registration records. Name.com, Inc. is the registrar on record today.
Checked in the last 30 daysOlder, dated recordFrom registration records
Registered 6 years ago · one registrar since Jul 1, 2020 · no registrant change on record since 2011 · last checked Nov 1, 2026.
Registration
RegisteredJun 30, 2020pullcm.com was registered on Jun 30, 2020.Source: RDAP, fetched Nov 1, 2026
AboutUs record
Current AboutUs recordJul 18, 2026 – Nov 1, 2026 (latest)Authority and Safety last refreshed Nov 1, 2026.Source: AboutUs checks
Registrar
Name.com, Inc.Name.com, Inc.Jul 1, 2020 – Sep 29, 2026 (latest)Registrar Name.com, Inc. (IANA 625) in the registration data recorded, first on Jul 1, 2020 and most recently on Sep 29, 2026.Source: RDAP, fetched Nov 1, 2026
Registrant
Registrant recordsJul 22, 2011 – Feb 10, 2026Registration records for pullcm.com are held from Jul 22, 2011 to Feb 10, 2026 (53 records). None shows a change of registrant. Privacy-service and redaction changes, renames of the same organization and new contacts at it are not counted.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
No registrant changes recorded, 2011–2026
Zone file
No nameserver records held, Jan 2014 – Jun 2020No nameserver records held, Jan 2014 – Jun 2020Nameservers: dsredirection.comOct 18, 2013 – Nov 1, 2013dsredirection.com (ns1.dsredirection.com, ns2.dsredirection.com) were the nameservers listed for pullcm.com at every ICANN zone-file snapshot AboutUs holds from Oct 18, 2013 to Nov 1, 2013 (snapshots exist for only part of 2013–2018).Source: ICANN zone-file snapshots, 2013–2018 (legacy archive)
Certificate
DigiCertOct 16, 2024 – Oct 15, 2025DigiCert issued 1 certificate for pullcm.com from Oct 16, 2024, the latest valid until Oct 15, 2025.Source: Certificate Transparency logs (crt.sh)DigiCert IncDigiCert IncOct 9, 2025 – Oct 16, 2026
201520202025Jan ’26Oct ’26← last 12 months, drawn wider
Every dated fact on this lifeline (13)
Jul 22, 2011 – Feb 10, 2026Registrant: Registration records for pullcm.com are held from Jul 22, 2011 to Feb 10, 2026 (53 records). None shows a change of registrant. Privacy-service and redaction changes, renames of the same organization and new contacts at it are not counted.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Oct 18, 2013 – Nov 1, 2013Zone file: dsredirection.com (ns1.dsredirection.com, ns2.dsredirection.com) were the nameservers listed for pullcm.com at every ICANN zone-file snapshot AboutUs holds from Oct 18, 2013 to Nov 1, 2013 (snapshots exist for only part of 2013–2018).Source: ICANN zone-file snapshots, 2013–2018 (legacy archive)
Jan 3, 2014Zone file: GoDaddy (ns41.domaincontrol.com, ns42.domaincontrol.com) were the nameservers listed for pullcm.com at every ICANN zone-file snapshot AboutUs holds from Jan 3, 2014 to Jan 3, 2014 (snapshots exist for only part of 2013–2018).Source: ICANN zone-file snapshots, 2013–2018 (legacy archive)
Jan 3, 2014Zone file: pullcm.com's nameservers moved from dsredirection.com to GoDaddy at some point between Nov 1, 2013 and Jan 3, 2014. Last seen at dsredirection.com: Nov 1, 2013 (ICANN zone-file snapshot). First seen at GoDaddy: Jan 3, 2014 (ICANN zone-file snapshot). AboutUs holds no nameserver records for the 2 months in between, so the date of the move is not known more closely.Source: Derived from the nameserver records on this lifeline (ICANN zone-file snapshot → ICANN zone-file snapshot)
Nameservers: GoDaddyJan 3, 2014GoDaddy (ns41.domaincontrol.com, ns42.domaincontrol.com) were the nameservers listed for pullcm.com at every ICANN zone-file snapshot AboutUs holds from Jan 3, 2014 to Jan 3, 2014 (snapshots exist for only part of 2013–2018).Source: ICANN zone-file snapshots, 2013–2018 (legacy archive)
DNS moved to GoDaddyJan 3, 2014pullcm.com's nameservers moved from dsredirection.com to GoDaddy at some point between Nov 1, 2013 and Jan 3, 2014. Last seen at dsredirection.com: Nov 1, 2013 (ICANN zone-file snapshot). First seen at GoDaddy: Jan 3, 2014 (ICANN zone-file snapshot). AboutUs holds no nameserver records for the 2 months in between, so the date of the move is not known more closely.Source: Derived from the nameserver records on this lifeline (ICANN zone-file snapshot → ICANN zone-file snapshot)
Nameservers: Amazon Route 53Nameservers: Amazon Route 53Jul 1, 2020 – Feb 10, 2026Registration records listed Amazon Route 53 nameservers (ns-1301.awsdns-34.org, ns-2007.awsdns-58.co.uk, ns-216.awsdns-27.com…) for pullcm.com from Jul 1, 2020 to Feb 10, 2026.Source: From registration records (WHOIS / RDAP archive, who.is)
DNS moved to Amazon Route 53Jul 1, 2020pullcm.com's nameservers moved from GoDaddy to Amazon Route 53 at some point between Jan 3, 2014 and Jul 1, 2020. Last seen at GoDaddy: Jan 3, 2014 (ICANN zone-file snapshot). First seen at Amazon Route 53: Jul 1, 2020 (registration record). AboutUs holds no nameserver records for the about 6 years in between, so the date of the move is not known more closely.Source: Derived from the nameserver records on this lifeline (ICANN zone-file snapshot → registration record)
Seen in the .com zone fileSep 8, 2026 – Nov 1, 2026 (latest)First seen in the .com zone file records AboutUs holds on Sep 8, 2026; latest sighting Nov 1, 2026. Nameservers on Nov 1, 2026: ns-1301.awsdns-34.org, ns-2007.awsdns-58.co.uk, ns-216.awsdns-27.com, ns-535.awsdns-02.net.Source: ICANN CZDS zone file, snapshot Nov 1, 2026
DigiCert Inc issued 1 certificate for pullcm.com from Oct 9, 2025, the latest valid until Oct 16, 2026.
Source: Certificate Transparency logs (crt.sh + AboutUs's own certificate-log reader)
Let's EncryptOct 8, 2026 – Nov 2, 2026Let's Encrypt issued 1 certificate for pullcm.com from Oct 8, 2026, the latest valid until Jan 6, 2027.Source: Certificate Transparency logs (crt.sh + AboutUs's own certificate-log reader)
Jun 30, 2020
Registration: pullcm.com was registered on Jun 30, 2020.Source: RDAP, fetched Nov 1, 2026
Jul 1, 2020 – Sep 29, 2026Registrar: Registrar Name.com, Inc. (IANA 625) in the registration data recorded, first on Jul 1, 2020 and most recently on Sep 29, 2026.Source: RDAP, fetched Nov 1, 2026
Jul 1, 2020 – Feb 10, 2026Zone file: Registration records listed Amazon Route 53 nameservers (ns-1301.awsdns-34.org, ns-2007.awsdns-58.co.uk, ns-216.awsdns-27.com…) for pullcm.com from Jul 1, 2020 to Feb 10, 2026.Source: From registration records (WHOIS / RDAP archive, who.is)
Jul 1, 2020Zone file: pullcm.com's nameservers moved from GoDaddy to Amazon Route 53 at some point between Jan 3, 2014 and Jul 1, 2020. Last seen at GoDaddy: Jan 3, 2014 (ICANN zone-file snapshot). First seen at Amazon Route 53: Jul 1, 2020 (registration record). AboutUs holds no nameserver records for the about 6 years in between, so the date of the move is not known more closely.Source: Derived from the nameserver records on this lifeline (ICANN zone-file snapshot → registration record)
Oct 16, 2024 – Oct 15, 2025Certificate: DigiCert issued 1 certificate for pullcm.com from Oct 16, 2024, the latest valid until Oct 15, 2025.Source: Certificate Transparency logs (crt.sh)
Oct 9, 2025 – Oct 16, 2026Certificate: DigiCert Inc issued 1 certificate for pullcm.com from Oct 9, 2025, the latest valid until Oct 16, 2026.Source: Certificate Transparency logs (crt.sh + AboutUs's own certificate-log reader)
Jul 18, 2026 – Nov 1, 2026AboutUs record: Authority and Safety last refreshed Nov 1, 2026.Source: AboutUs checks
Sep 8, 2026 – Nov 1, 2026Zone file: First seen in the .com zone file records AboutUs holds on Sep 8, 2026; latest sighting Nov 1, 2026. Nameservers on Nov 1, 2026: ns-1301.awsdns-34.org, ns-2007.awsdns-58.co.uk, ns-216.awsdns-27.com, ns-535.awsdns-02.net.Source: ICANN CZDS zone file, snapshot Nov 1, 2026
Oct 8, 2026 – Nov 2, 2026Certificate: Let's Encrypt issued 1 certificate for pullcm.com from Oct 8, 2026, the latest valid until Jan 6, 2027.Source: Certificate Transparency logs (crt.sh + AboutUs's own certificate-log reader)
Automated safety checks
DNS (failed)
Add a public A or AAAA record so the domain resolves.
HTTPS (failed)
Make sure the site responds over HTTPS with a valid certificate.
AboutUs has not vetted this site. Everything below is what we could measure automatically. Anything you do on the site — paying, sharing personal details, downloading — is between you and the site, not AboutUs.
Current facts
Latest available measurements; dated entries retain their dates. These are measurements, not an endorsement of the site.
latest result
Domain registered Jun 30, 2020 — 6 years old.
latest result
Registrar on record: Name.com, Inc. — unchanged since AboutUs began tracking (Jul 23, 2026).
Authority 36/100— ahead of 36% of the August 2026 scored sampleSome caution flags
Why this authority score
36 is a percentile: higher than 36% of sites we score.
How it's calculated
Prominence (Tranco rank #2,127; Open PageRank 0.1/10)+9
Verified continuity: 6.3 years (RDAP registration)+6
Security & email hygiene+1
Calibration adjustment (published map)+5
Model score: 21/99 — what these reason lines add up to.
Published Authority (percentile): 36/100 — this site's rank against the August 2026 scored sample. Public Authority is capped at 99.
Safety evidence
Retained threat-feed result (recorded about 1 days ago); name-similarity check available (recorded about 1 days ago); 3/3 transport and email checks available (oldest recorded about 1 days ago). This is evidence coverage, not a probability that a website is safe.
Recorded HTTPS check did not confirm a valid connection
No MX and no DMARC (mild)
Site history
Dated record — historical facts always carry their date.