monitorconnect.com

Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .

Online · 200SafeSSL: 175 days left15 years old

One re-check per domain each UTC day.

85

monitorconnect.com was registered on 10 Mar 2011 via Network Solutions, LLC and the registry expiry is 10 Mar 2031. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/monitorconnect.com.

monitorconnect.com publishes 2 nameservers. DNSSEC is not signed.

monitorconnect.com has 2 IPv4 addresses (20.118.138.136, 20.150.247.0). The geolocation database places 20.118.138.136 in Phoenix, United States.

The TLS certificate from GeoTrust TLS RSA CA G1 is valid and has 175 days left (TLS 1.3). The homepage answered HTTP 200.

Tech detection named Contact Form 7, Google Analytics, HSTS, Magnific Popup, MonsterInsights, MySQL, Nginx, PHP, Slider Revolution, W3 Total Cache, WordPress, jQuery and wpBakery. The fingerprints ran on the homepage that was already downloaded.

No safety warning was recorded for monitorconnect.com in the checks that ran.

Domain · RDAP/WHOIS

monitorconnect.com was registered on 10 Mar 2011 via Network Solutions, LLC. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/monitorconnect.com.

Registeredsince 10 Mar 2011
Created10 March 2011
Updated9 January 2026
Expires10 March 2031
RegistrarNetwork Solutions, LLC
Statusclient transfer prohibited
Nameserversns19.worldnic.com, ns20.worldnic.com
DNSSECno
Sourcehttps://rdap.verisign.com/com/v1/domain/monitorconnect.com

monitorconnect.com carries the status "client transfer prohibited". The registrar has asked the registry to refuse a transfer to another registrar. The status is a lock on the domain object. It is not evidence about the content of the site.

Nameserver ns19.worldnic.com is published for monitorconnect.com in the registration record from https://rdap.verisign.com/com/v1/domain/monitorconnect.com.

Nameserver ns20.worldnic.com is published for monitorconnect.com in the registration record from https://rdap.verisign.com/com/v1/domain/monitorconnect.com.

DNS

monitorconnect.com has 2 address records, 2 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.

A20.118.138.136, 20.150.247.0
AAAA—
NSns19.worldnic.com, ns20.worldnic.com
MXmx001.netsol.xion.oxcs.net (10), mx002.netsol.xion.oxcs.net (10)
SPFpresent
DMARCpresent
CAA—
Wildcardoff
DNSSECnot signed
Resolver1.1.1.1:53

The SPF text record at monitorconnect.com is "v=spf1 include:_spf.smtp.com include:mail.zendesk.com include:spf.cloudus.oxcs.net -all".

The DMARC text record at _dmarc.monitorconnect.com is "v=DMARC1;p=reject;sp=reject;rua=mailto:[email protected];ruf=mailto:[email protected];fo=1;".

IPv4 address 20.118.138.136 answers for monitorconnect.com at resolver 1.1.1.1:53.

IPv4 address 20.150.247.0 answers for monitorconnect.com at resolver 1.1.1.1:53.

Mail exchanger mx001.netsol.xion.oxcs.net has preference 10.

Mail exchanger mx002.netsol.xion.oxcs.net has preference 10.

Hosting and geo

monitorconnect.com is placed in Phoenix, United States by the local geolocation database (db-ip).

Address20.118.138.136
CountryUnited States
CityPhoenix
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for monitorconnect.com is valid, with 175 days left and 1 subject alternative name. Source: tls:443.

IssuerGeoTrust TLS RSA CA G1
Subjectmonitorconnect.com
Valid from24 October 2026
Valid until24 April 2027
Days left175
SAN count1
ProtocolTLS 1.3
Sourcetls:443

Subject alternative names: monitorconnect.com.

Tech stack

Tech detection checked the fetched homepage and named 13 products. Source: wappalyzergo.

  • Contact Form 7 · WordPress plugins, Form builders
  • Google Analytics · Analytics
  • HSTS · Security
  • Magnific Popup · JavaScript libraries
  • MonsterInsights · WordPress plugins, Analytics
  • MySQL · Databases
  • Nginx · Web servers, Reverse proxies
  • PHP · Programming languages
  • Slider Revolution · Widgets, Photo galleries
  • W3 Total Cache · Caching, WordPress plugins
  • WordPress · CMS, Blogs
  • jQuery · JavaScript libraries
  • wpBakery · Page builders, WordPress plugins

Contact Form 7 is filed under WordPress plugins, Form builders.

Google Analytics is filed under Analytics.

HSTS is filed under Security.

Magnific Popup is filed under JavaScript libraries.

MonsterInsights is filed under WordPress plugins, Analytics.

MySQL is filed under Databases.

Nginx is filed under Web servers, Reverse proxies.

PHP is filed under Programming languages.

Slider Revolution is filed under Widgets, Photo galleries.

W3 Total Cache is filed under Caching, WordPress plugins.

WordPress is filed under CMS, Blogs.

jQuery is filed under JavaScript libraries.

wpBakery is filed under Page builders, WordPress plugins.

On-page checks

The homepage returned HTTP 200 in 576 ms. The target title is 116 characters and the page has 4 H1 headings.

Status200
TTFB576 ms
Title length116 no
Quoted title"MonitorConnect – MonitorConnect is a self-reporting and reminder system for court ordered supervision and probation."
Meta descriptionnone no
H1 count4
HSTSyes yes
CSPno
X-Frame-OptionsSAMEORIGIN
Robots metamax-image-preview:large
Canonicalhttps://www.monitorconnect.com/
Languageen-US
Links38
Images13
Faviconyes

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 monitorconnect.com is clear, and URLhaus is clear. Source: family DNS and local lists.

Family DNSclear
URLhausclear
UT1—
Web Risknot run
Sourcefamily DNS and local lists
HSTSyes
CSPno

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 10 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: geo city changed from empty to Phoenix.
  • October 2026: geo country changed from empty to United States.

Questions

Is monitorconnect.com 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 monitorconnect.com?

monitorconnect.com is placed in Phoenix, United States.

When does monitorconnect.com expire?

monitorconnect.com expires on 10 March 2031 according to https://rdap.verisign.com/com/v1/domain/monitorconnect.com.

Who owns monitorconnect.com?

The registry did not return a person or a company for monitorconnect.com. RDAP often redacts the registrant. The registrar on file is Network Solutions, LLC.

Sources

  • RDAP source https://rdap.verisign.com/com/v1/domain/monitorconnect.com at 2026-10-30T14:04:42Z
  • DNS source 1.1.1.1:53 at 2026-10-30T14:04:42Z
  • TLS source tls:443 at 2026-10-30T14:04:42Z
  • HTTP source https://monitorconnect.com/ at 2026-10-30T14:04:42Z
  • Tech source wappalyzergo at 2026-10-30T14:04:42Z
  • Geo source db-ip at 2026-10-30T14:04:42Z
  • Safety source family DNS and local lists at 2026-10-30T14:04:42Z

Methodology

Related reports

No other indexable reports share this TLD, host, or registrar yet.

.com Network Solutions, LLC

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.

Removal policy

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.