Dataweaz

hmhco.com

Summary

Registrar
Network Solutions, LLC
Status
clientTransferProhibited
Created on
February 18, 2007
Expires on
February 18, 2027
Name servers
ns-341.awsdns-42.com, ns-951.awsdns-54.net, ns-1193.awsdns-21.org, ns-1900.awsdns-45.co.uk
Mail servers
us-smtp-inbound-2.mimecast.com, us-smtp-inbound-1.mimecast.com
SPF
Soft

Spoofing protection (DMARC)

Quarantine

E-mails spoofing this domain are sent to spam.

DMARC tells mail servers what to do with an e-mail that claims to come from hmhco.com but fails SPF and DKIM checks.

Policy
Quarantine
Subdomain policy
Quarantine
Messages covered
100%
DKIM alignment
Relaxed
SPF alignment
Relaxed
Aggregate reports
—
Failure reports
—

Record

v=DMARC1; p=quarantine; pct=100

Authorized senders (SPF)

Soft

E-mails sent by any other server are accepted but flagged as suspicious.

SPF lists the servers allowed to send e-mails for hmhco.com.

RuleValueResult
ip4209.235.126.1Allowed
ip4209.235.126.2Allowed
ip4209.235.126.7Allowed
ip4209.235.126.8Allowed
ip4209.235.126.9Allowed
ip4209.235.126.10Allowed
include_netblocks.hmhco.comAllowed
include_spf.salesforce.comAllowed
includeus._netblocks.mimecast.comAllowed
all—Suspicious

Top-level DNS lookups: 3 of 10 allowed

Record

v=spf1 ip4:209.235.126.1 ip4:209.235.126.2 ip4:209.235.126.7 ip4:209.235.126.8 ip4:209.235.126.9 ip4:209.235.126.10 include:_netblocks.hmhco.com include:_spf.salesforce.com include:us._netblocks.mimecast.com ~all

E-mail signing (DKIM)

DKIM keys published by hmhco.com under the most common selectors. Other keys may exist under selectors specific to each sending service.

SelectorLikely serviceKeyStatus
selector2Microsoft 365RSA 1024 bits · shortActive
s1SendGridRSA 2048 bitsActive
s2SendGridRSA 1024 bits · shortActive

RSA keys shorter than 2048 bits, called short keys, are discouraged: they are easier to break.

MX, SPF, DKIM and DMARC: the e-mail records

Four DNS records make a domain's e-mail work. MX says where e-mails sent to hmhco.com arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from hmhco.com was really sent by this domain, which protects it against spoofing.

MX

An MX (Mail Exchanger) record designates a server that receives e-mails sent to the domain. When someone writes to an @hmhco.com address, their mail server queries the DNS for the domain's MX records, then delivers the message to the server they point to.

Example record

hmhco.com  MX  10 mx1.hmhco.com.
hmhco.com  MX  20 mx2.hmhco.com.

What the record contains

10, 20
Priority: the server with the lowest number is tried first. Servers with equal priority share the load.
mx1.hmhco.com.
Host name of the mail server. It must point to an A or AAAA record: an IP address or an alias (CNAME) is not allowed here.
0 .
An MX "0 .", called a null MX, declares that the domain accepts no e-mail: sending servers give up at once instead of retrying.

Declaring at least two servers with different priorities avoids losing e-mails during an outage: sending servers retry for several days and fall back on the backup server. Without any MX, they try to deliver directly to the IP address of the domain.

SPF

SPF (Sender Policy Framework) is a TXT record listing the servers allowed to send e-mails on behalf of the domain. The receiving server checks that the sender is on this list. The final "all" rule says what to do with other servers: reject them (-all), flag their e-mails as suspicious (~all) or make no decision (?all).

Example record

hmhco.com  TXT  "v=spf1 mx include:_spf.google.com ip4:192.0.2.10 -all"

What the record contains

v=spf1
Identifies the record as an SPF policy. It must come first.
ip4, ip6
Allows a specific IP address or an address range, for example ip4:192.0.2.0/24.
a, mx
Allows the addresses of the domain itself (A record) or those of its mail servers (MX).
include
Allows the servers of another domain, usually a sending service: include:_spf.google.com for Google Workspace.
-all, ~all
Final rule, applied to every other server. Its qualifier decides what happens to them: - rejects them, ~ flags their e-mails as suspicious, ? makes no decision, + accepts them (avoid it).

A domain must publish only one SPF record, and its evaluation cannot exceed 10 DNS lookups (include, a, mx, exists, redirect). Beyond that, mail servers treat it as invalid.

DKIM

DKIM (DomainKeys Identified Mail) signs every outgoing e-mail with a private key. The matching public key is published in a TXT record at selector._domainkey.hmhco.com, so the recipient can check that the message really comes from the domain and was not altered on the way. The selector is chosen by each sending service and cannot be guessed: Dataweaz checks the most common ones (Google Workspace, Microsoft 365, Mailchimp, SendGrid…), so a key published under another selector may exist without appearing here.

Example record

google._domainkey.hmhco.com  TXT  "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA…"

What the record contains

v=DKIM1
Protocol version. Optional but recommended, in which case it must come first.
k
Key algorithm: rsa, the most common, or ed25519.
p
Public key, base64-encoded. An empty value means the key has been revoked.
t
Flags: y marks a key in testing, whose failures must not be penalized; s forbids its use for subdomains.

Each sending service publishes its key under its own selector (google, selector1, k1…), which allows several keys and seamless rotation. A 2048-bit RSA key is recommended today.

DMARC

DMARC (Domain-based Message Authentication, Reporting and Conformance) builds on SPF and DKIM. Published on _dmarc.hmhco.com, it tells mail servers what to do with an e-mail that fails these checks (let it through, send it to spam or reject it) and where to send reports.

Example record

_dmarc.hmhco.com  TXT  "v=DMARC1; p=quarantine; rua=mailto:[email protected]; adkim=r; aspf=r"

What the record contains

v=DMARC1
Identifies the record as a DMARC policy. It must come first.
p
Policy applied to e-mails that fail the checks: none (monitoring only), quarantine (spam folder) or reject.
sp
Subdomain policy. Without it, subdomains follow the domain's policy.
rua
Address that receives daily aggregate reports about e-mails sent on behalf of the domain, whether they pass the checks or not.
ruf
Address that receives detailed failure reports, message by message. Few providers still send them.
pct
Percentage of e-mails subject to the policy, for a gradual rollout. 100 by default.
adkim, aspf
DKIM and SPF alignment: r (relaxed, a subdomain of the same domain is enough) or s (strict, the domain must be identical).

To roll out DMARC without blocking legitimate e-mails, start with p=none and an rua address, analyze the reports to find every service sending on behalf of the domain, then move to quarantine and finally to reject.

DNS records of hmhco.com

IP addresses (A and AAAA)

An A record maps the domain name to an IPv4 address: the address of the server that browsers contact to display the website. The AAAA record does the same for an IPv6 address. A domain can have several of them to spread visits across several servers.

Name servers (NS)

NS records designate the authoritative DNS servers of the domain: they answer every question about its other records (A, MX, TXT…). They are provided by the registrar, the hosting provider or a dedicated DNS service, and several servers are declared so that the domain keeps working if one of them fails.

ServerIP address
ns-341.awsdns-42.com205.251.193.85
ns-951.awsdns-54.net205.251.195.183
ns-1193.awsdns-21.org205.251.196.169
ns-1900.awsdns-45.co.uk205.251.199.108

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @hmhco.com addresses. Each server has a priority: the one with the lowest number is tried first, the others take over if it fails. Without an MX record, the domain cannot receive e-mails.

PriorityServerIP address
5us-smtp-inbound-2.mimecast.com170.10.128.242
5us-smtp-inbound-1.mimecast.com170.10.128.221

TXT records

TXT records hold free text. They are used to prove ownership of the domain to online services (Google, Microsoft, Facebook…) and to publish e-mail security rules: SPF on the domain itself, DMARC on _dmarc.hmhco.com.

NameContent
hmhco.com_yrydfmt6ek9t9k9oiffq7j710sdp5r2
hmhco.comMS=ms65451366
hmhco.comgoogle-site-verification=jWaPYj9EqDhNlqii90MwSAGGqILGT3qvjv3sc9AjwVk
hmhco.com_reegr6qrngjjfjigyyak4y4149z96f0
hmhco.com_zjf8wvnzc5hzfuordx7qti6vz2lo9dd
hmhco.comdocusign_verification=dm5d176s-eg0e-l9sg-abdi-hd56sz2tt0wc
hmhco.comatlassian-domain-verification=BNYS2ZxDgYF0MABftk2Zoz5k5a1O4ISi5g0vBS7vRKxvosDsl020tMm88EaCzkFE
hmhco.comsmartsheet-site-validation=Y9J8B1EtJP8RjvrCy7bJNAGuwfZwPPw0
hmhco.comcisco-ci-domain-verification=1e77c8c1819f3634ebaf3190e828520ae8b44db10725f96505c5668952e1a16a
hmhco.comdocusign=9a0d3862-ce0a-4272-be65-e9d0ee8109b9
hmhco.com_o890m8p0326f3zjpvgg9visthiabpps
hmhco.comdocusignv=52c16912-2c65-4f50-b613-fa56c465c707
hmhco.comv=spf1 ip4:209.235.126.1 ip4:209.235.126.2 ip4:209.235.126.7 ip4:209.235.126.8 ip4:209.235.126.9 ip4:209.235.126.10 include:_netblocks.hmhco.com include:_spf.salesforce.com include:us._netblocks.mimecast.com ~all
hmhco.comcanva-site-verification=XAvMwkZKNaFlNW4YQojH3g
hmhco.comfe12f446-397f-4147-8aaa-a09a152e0e4f
hmhco.comglobalsign-domain-verification=1111620e7587ddb0d56bfd6fcd6d4ae4
hmhco.com_9sie6t2ppawjloiuavjlv2dx3qite9b
hmhco.comgoogle-site-verification=9xAnKLlO-n0fb9ivg6304GUrAOYJzqF00f9NzD0YqwU
hmhco.comextensis-domain-verification=283f9982-b8c8-4996-8611-6c3b16ca80a8
hmhco.comjamf-site-verification=ypSPyAynUFATrS5zB59L9g
hmhco.comadobe-idp-site-verification=dcee0a2f77d8062795e70509a65d7f6913450b5485badb2058f23588f060c8b9
hmhco.commiro-verification=788279500223085801eb9b034064d4a96bdabaf3
hmhco.comanthropic-domain-verification-5724sj=l3u5vPhGuyCjhW0PY7kwoP6Xm
hmhco.com_xk90kd0yh344144zsllem3xd0tur9ye
hmhco.comcanva-site-verification=nDn0iJqSi1AhFR_cAw5isQ
hmhco.comatlassian-domain-verification=CBbj/iXZ5lGubFrU2QeWACCkSiIcanWzOa3PxRDfyjxeJsv4d/vf4xiiortak0h1
hmhco.com_9y67qztkt2btxbaml8r2vjg40pzjd3c
hmhco.comgoogle-site-verification=WAHW1EO8Bhocy1PlQISnzb50g26m17-znBENRYcynKI
hmhco.comopenai-domain-verification=dv-LvPgut8vxG5Id4c62TexDLU0
hmhco.combrowserstack-domain-verification=1b67a2d1-17fb-4c1c-9767-3d0bc7d1665e
hmhco.com49NBsw/Se/C6JS0bY1ERCAIm4lXSNiDJB3VJ4548dGRG3LGlCjuddY3HFB6JrGLJJns1X0QVEaK3c3mAxiDdpA==
hmhco.comamazonses:zvT1yYoxLfumWiB6ESAVrkUzwpwo6ClRCUxHEsYjaFY=
hmhco.comglobalsign-domain-verification=ace3534fbff0e03574dcd4f8bb8848b7
hmhco.com_88p140xxu23fri4pwb8p9kiy0t0aq89
hmhco.comcanva-site-verification=7BqVD8X2bt48CNLNCochRw
hmhco.compexip-ms-tenant-domain-verification=f05dded6-08d7-4594-b27b-6d2f601a4919
hmhco.comfluency-domain-verification-p3edjb=C69njd7xl6pYYPFQifwU9QmUE
hmhco.comglobalsign-domain-verification=C7DBEB65A538212CBB663B0F083CCB9B
hmhco.comOSSRH-77297
hmhco.comfacebook-domain-verification=j9y57ganvf1td5819xs1y7ro1oaocs
hmhco.comapple-domain-verification=P7EQHRcSw1MEhYAw
hmhco.compendo-domain-verification=-c2MowabHj26bsKA847E49izAIM
hmhco.comglobalsign-domain-verification=A5690202F4D1340FC95C7147711395FE
_dmarc.hmhco.comv=DMARC1; p=quarantine; pct=100
selector2._domainkey.hmhco.comv=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDAgwmXCQZtAlCaOrkFCzfHYaE6iWqWE591ln9pq0W6RvA8utre3bWDJCe1GX8RK4oHcWQfrh5FdmKss0mQET5dxw6XWDOgJmJTTJ1Z+NjVud3btm7YGIV1kwgN85tdQXuOTlo91848A8QuMNtNHS2mwY+SldYSRc80IuUq3qisHQIDAQAB;
s1._domainkey.hmhco.comk=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAp1zlr7IQEyuophSls5294VTUD3nxR4cCIgluyffWSbnVC4+gbmDZPtwFKpFasMi8fLQNj9xdiJL6jbq8NZ1oEd7nMvY+JKdblPVPSWDDzVrGCkRUTMrZrYh23DpIumgRHrFpThjhIWReQ5R4v2SFzZLlk9wvWHZ1e2TOJgAxbVpFMDo0Z+XMs0AyrCkSKvq9ZomUcIDoU+w14FQbcy6uWi5GhD2Edb2+HfWMDlSROaMZUFFOI9WFLuXgHDCB+sf+OvMWfMrfSeUtPthtXtwyyoMAb9FrUMQ24d3wBtoyWXlt4cgdAKR8JSV/t2m3lGFkQEMHh8aMg2xT6O5goGQQ2QIDAQAB
s2._domainkey.hmhco.comk=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDbdcFc35f4ceTkhV+92lWNz32qCKT4QCIgRSwe7xzgHU3rN6C6+TpY3Z5kWQ2JOL7hBwUvgZmr0wdWBO3/vxFS3ixScGXjiqRHE4sIPaximCHneggj9CWgZgb36MIZAQ/aC29+eWzqh1OI7i65/AKj8GPIBfrausyxsWx0uhBNkwIDAQAB

Related IP addresses

IPv4 addresses used by hmhco.com: website, name servers, mail servers and senders authorized by SPF.

IP addressUsed for/24 block
45.60.101.203Website45.60.101.0/24
45.60.11.203Website45.60.11.0/24
205.251.193.85Name server ns-341.awsdns-42.com205.251.193.0/24
205.251.195.183Name server ns-951.awsdns-54.net205.251.195.0/24
205.251.196.169Name server ns-1193.awsdns-21.org205.251.196.0/24
205.251.199.108Name server ns-1900.awsdns-45.co.uk205.251.199.0/24
170.10.128.242Mail server us-smtp-inbound-2.mimecast.com170.10.128.0/24
170.10.128.221Mail server us-smtp-inbound-1.mimecast.com170.10.128.0/24
209.235.126.1Authorized by SPF209.235.126.0/24
209.235.126.2Authorized by SPF209.235.126.0/24
209.235.126.7Authorized by SPF209.235.126.0/24
209.235.126.8Authorized by SPF209.235.126.0/24
209.235.126.9Authorized by SPF209.235.126.0/24
209.235.126.10Authorized by SPF209.235.126.0/24

WHOIS of the domain hmhco.com

Domain Name: HMHCO.COM
   Registry Domain ID: 823415015_DOMAIN_COM-VRSN
   Registrar WHOIS Server: whois.networksolutions.com
   Registrar URL: http://networksolutions.com
   Updated Date: 2026-02-03T09:30:06Z
   Creation Date: 2007-02-18T14:24:38Z
   Registry Expiry Date: 2027-02-18T14:24:38Z
   Registrar: Network Solutions, LLC
   Registrar IANA ID: 2
   Registrar Abuse Contact Email: [email protected]
   Registrar Abuse Contact Phone: +1.8777228662
   Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
   Name Server: NS-1193.AWSDNS-21.ORG
   Name Server: NS-1900.AWSDNS-45.CO.UK
   Name Server: NS-341.AWSDNS-42.COM
   Name Server: NS-951.AWSDNS-54.NET
   DNSSEC: unsigned
   URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2026-10-02T08:46:13Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar.  Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability.  VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.

The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.