commentguard.io
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 79 days left4 years old
75
commentguard.io was registered on 12 Feb 2022 via Key-Systems GmbH and the registry expiry is 12 Feb 2027. WHOIS data came from RDAP at https://rdap.identitydigital.services/rdap/domain/commentguard.io.
commentguard.io publishes 2 nameservers. DNSSEC is not signed.
commentguard.io has 4 IPv4 addresses (34.149.36.179, 34.160.17.71, 35.190.31.54, 35.244.153.44). The geolocation database places 34.149.36.179 in Kansas City, United States.
The TLS certificate from YR2 is valid and has 79 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Draftpress HFCM, Google Tag Manager, MySQL, Nginx, PHP, Thrive Architect, WordPress, imagesLoaded, jQuery and jQuery Migrate. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for commentguard.io in the checks that ran.
Domain · RDAP/WHOIS
commentguard.io was registered on 12 Feb 2022 via Key-Systems GmbH. The registry returned 1 status value and 2 nameservers from https://rdap.identitydigital.services/rdap/domain/commentguard.io.
| Registered | since 12 Feb 2022 |
|---|---|
| Created | 12 February 2022 |
| Updated | 11 August 2026 |
| Expires | 12 February 2027 |
| Registrar | Key-Systems GmbH |
| Status | active |
| Nameservers | ns1.siteground.net, ns2.siteground.net |
| DNSSEC | no |
| Source | https://rdap.identitydigital.services/rdap/domain/commentguard.io |
Nameserver ns1.siteground.net is published for commentguard.io in the registration record from https://rdap.identitydigital.services/rdap/domain/commentguard.io.
Nameserver ns2.siteground.net is published for commentguard.io in the registration record from https://rdap.identitydigital.services/rdap/domain/commentguard.io.
DNS
commentguard.io has 4 address records, 3 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 34.149.36.179, 34.160.17.71, 35.190.31.54, 35.244.153.44 |
|---|---|
| AAAA | — |
| NS | ns1.siteground.net, ns2.siteground.net |
| MX | mx10.antispam.mailspamprotection.com (10), mx20.antispam.mailspamprotection.com (20), mx30.antispam.mailspamprotection.com (30) |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at commentguard.io is "v=spf1 include:_spf.mailersend.net +a +mx +ip4:35.209.152.28 include:mailgun.org include:commentguard.io.spf.auto.dnssmarthost.net ~all".
The DMARC text record at _dmarc.commentguard.io is "v=DMARC1; p=none; aspf=r; adkim=r;".
IPv4 address 34.149.36.179 answers for commentguard.io at resolver 1.1.1.1:53.
IPv4 address 34.160.17.71 answers for commentguard.io at resolver 1.1.1.1:53.
IPv4 address 35.190.31.54 answers for commentguard.io at resolver 1.1.1.1:53.
IPv4 address 35.244.153.44 answers for commentguard.io at resolver 1.1.1.1:53.
Mail exchanger mx10.antispam.mailspamprotection.com has preference 10.
Mail exchanger mx20.antispam.mailspamprotection.com has preference 20.
Mail exchanger mx30.antispam.mailspamprotection.com has preference 30.
Hosting and geo
commentguard.io is placed in Kansas City, United States by the local geolocation database (db-ip).
| Address | 34.149.36.179 |
|---|---|
| Country | United States |
| City | Kansas City |
| Source | db-ip |
SSL/TLS
The certificate for commentguard.io is valid, with 79 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YR2 |
|---|---|
| Subject | *.commentguard.io |
| Valid from | 20 October 2026 |
| Valid until | 18 January 2027 |
| Days left | 79 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.commentguard.io, commentguard.io.
Tech stack
Tech detection checked the fetched homepage and named 10 products. Source: wappalyzergo.
- Draftpress HFCM · WordPress plugins
- Google Tag Manager · Tag managers
- MySQL · Databases
- Nginx · Web servers, Reverse proxies
- PHP · Programming languages
- Thrive Architect · WordPress plugins, Page builders
- WordPress · CMS, Blogs
- imagesLoaded · JavaScript libraries
- jQuery · JavaScript libraries
- jQuery Migrate · JavaScript libraries
Draftpress HFCM is filed under WordPress plugins.
Google Tag Manager is filed under Tag managers.
MySQL is filed under Databases.
Nginx is filed under Web servers, Reverse proxies.
PHP is filed under Programming languages.
Thrive Architect is filed under WordPress plugins, Page builders.
WordPress is filed under CMS, Blogs.
imagesLoaded is filed under JavaScript libraries.
jQuery is filed under JavaScript libraries.
jQuery Migrate is filed under JavaScript libraries.
On-page checks
The homepage returned HTTP 200 in 12 ms. The target title is 55 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 12 ms |
| Title length | 55 yes |
| Quoted title | "CommentGuard | Facebook & Instagram Moderation Software" |
| Meta description | "CommentGuard is the #1 comment moderation software for Facebook & Instagram posts and ads. Free 7-day trial. No credit card required." yes |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1 |
| Canonical | https://commentguard.io/ |
| Language | en-US |
| Links | 14 |
| Images | 44 |
| Favicon | no |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Security
Family DNS for commentguard.io is clear, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | clear |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
Google Web Risk did not run. No API key is configured, and this report does not invent a clean result from that service.
Score breakdown
Availability 25 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.
TLS 20 of 20. A valid certificate, with extra points when it has at least 14 days left.
DNS hygiene 10 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 0 of 15. HSTS, CSP, and X-Frame-Options or CSP frame-ancestors.
Safety lists 15 of 15. Points only when the checks ran and came back clean. Unknown is not clean.
Domain age 5 of 5. Five points at one year, two points at 30 days.
Change history
- October 2026: rdap created changed from 2022-02-12T14:25:21Z to 2022-02-12T14:25:21.875Z.
- October 2026: rdap dnssec changed from unknown to no.
- October 2026: rdap expires changed from 2027-02-12T14:25:21Z to 2027-02-12T14:25:21.875Z.
- October 2026: rdap statuses changed from ok to active.
- October 2026: rdap updated changed from 2026-08-11T22:17:31Z to 2026-08-11T22:17:31.267Z.
- October 2026: dns a changed from 34.160.17.71,34.160.81.203,35.227.194.51,35.244.153.44 to 34.149.36.179,34.160.17.71,35.190.31.54,35.244.153.44.
- October 2026: geo city changed from empty to Kansas City.
- October 2026: geo country changed from empty to United States.
Questions
Is commentguard.io safe?
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
Who hosts commentguard.io?
commentguard.io is placed in Kansas City, United States.
When does commentguard.io expire?
commentguard.io expires on 12 February 2027 according to https://rdap.identitydigital.services/rdap/domain/commentguard.io.
Who owns commentguard.io?
The registry did not return a person or a company for commentguard.io. RDAP often redacts the registrant. The registrar on file is Key-Systems GmbH.
Sources
- RDAP source https://rdap.identitydigital.services/rdap/domain/commentguard.io at 2026-10-30T14:33:50Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:33:50Z
- TLS source tls:443 at 2026-10-30T14:33:50Z
- HTTP source https://commentguard.io/ at 2026-10-30T14:33:50Z
- Tech source wappalyzergo at 2026-10-30T14:33:50Z
- Geo source db-ip at 2026-10-30T14:33:50Z
- Safety source family DNS and local lists at 2026-10-30T14:33:50Z
Related reports
No other indexable reports share this TLD, host, or registrar yet.
Owner of this site?
Ask for a correction or for the report to be removed from search. Public DNS facts stay on the page. An optional badge is not inserted for you.
How to read this report
The sentences under each heading are filled from the latest snapshot. If a collector had nothing to say, that sentence is left out. The target site's own title and meta description, when shown, are quoted as measurements. They are not this page's title. Change history only lists a difference between two snapshots, so the first check starts the clock and later edits are the history. A malware blocklist is the only reason the homepage body is skipped. That fact stays on the report. It does not by itself drop the page from the sitemap or from related-report links.