Dataweaz

iamp.us

Summary

Registrar
GoDaddy.com, LLC
Status
clientUpdateProhibited
Created on
July 30, 2014
Expires on
July 30, 2027
Name servers
pdns06.domaincontrol.com, pdns05.domaincontrol.com
Mail servers
smtp.secureserver.net, mailstore1.secureserver.net
DMARC
Reject

Spoofing protection (DMARC)

Reject

E-mails spoofing this domain are rejected.

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

Policy
Reject
Subdomain policy
Reject
Messages covered
100%
DKIM alignment
Relaxed
SPF alignment
Relaxed
Aggregate reports
[email protected]
Failure reports
[email protected]

Record

v=DMARC1; p=reject; pct=100; rua=mailto:[email protected]; ruf=mailto:[email protected]

Authorized senders (SPF)

Strict

E-mails sent by any other server are rejected.

SPF lists the servers allowed to send e-mails for iamp.us.

RuleValueResult
a—Allowed
mx—Allowed
ip463.174.23.0/24Allowed
ip4206.210.87.0/29Allowed
ip4206.210.87.8/29Allowed
ip4206.210.87.16/29Allowed
ip4206.210.87.24/29Allowed
ip4206.210.91.24/29Allowed
ip4206.210.91.80/29Allowed
includesecureserver.netAllowed
all—Rejected

Top-level DNS lookups: 3 of 10 allowed

Record

v=spf1 a mx ip4:63.174.23.0/24 ip4:206.210.87.0/29 ip4:206.210.87.8/29 ip4:206.210.87.16/29 ip4:206.210.87.24/29 ip4:206.210.91.24/29 ip4:206.210.91.80/29 include:secureserver.net -all

E-mail signing (DKIM)

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

SelectorLikely serviceKeyStatus
default—RSA 2048 bitsActive

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 iamp.us arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from iamp.us 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 @iamp.us 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

iamp.us  MX  10 mx1.iamp.us.
iamp.us  MX  20 mx2.iamp.us.

What the record contains

10, 20
Priority: the server with the lowest number is tried first. Servers with equal priority share the load.
mx1.iamp.us.
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

iamp.us  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.iamp.us, 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.iamp.us  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.iamp.us, 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.iamp.us  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 iamp.us

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.

TypeIP address
A63.174.23.41

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
pdns06.domaincontrol.com173.201.78.52
pdns05.domaincontrol.com97.74.110.52

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @iamp.us 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
0smtp.secureserver.net92.204.80.20
10mailstore1.secureserver.net92.204.80.19

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.iamp.us.

NameContent
iamp.usD7083962
iamp.usgoogle-site-verification=9Fc-WRuf-hB4h5hBCSDCRvF4HYXnUcmEQQ7HFTS1na8
iamp.usv=spf1 a mx ip4:63.174.23.0/24 ip4:206.210.87.0/29 ip4:206.210.87.8/29 ip4:206.210.87.16/29 ip4:206.210.87.24/29 ip4:206.210.91.24/29 ip4:206.210.91.80/29 include:secureserver.net -all
_dmarc.iamp.usv=DMARC1; p=reject; pct=100; rua=mailto:[email protected]; ruf=mailto:[email protected]
default._domainkey.iamp.usk=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAnxfCVHeKbuPkLsuESuXsRxnaLXdD7zQQr+JlDzyzSECeWbYlBqJP5pJziZ3D2wjMEgRJ9LqW/Q2KoO+wTu6NiIYjMi9EFcjCZi6CoRtGQ5055wMV4XsrruK2Lggct6cUOP/ermRW+nu44ejGzKVLMhbFK5uDgsMsJtspBiZo2nFFi30ELCSAql0miNxqF8ajVVpnPljvV8" "/Uav8MLkZ1+PC2YhpDvygApFsfglUqo29InG70oy9eaUmfLsqetlchy8RxYMmj/6RqBEphPzBcp/e5t//33QkVhprk58ylva1/33ZAnoL/vPtop17pFefuM1jpVEu3BNX3zF9RoEKPSwIDAQAB

Related IP addresses

IPv4 addresses used by iamp.us: website, name servers, mail servers and senders authorized by SPF.

IP addressUsed for/24 block
63.174.23.41Website63.174.23.0/24
173.201.78.52Name server pdns06.domaincontrol.com173.201.78.0/24
97.74.110.52Name server pdns05.domaincontrol.com97.74.110.0/24
92.204.80.20Mail server smtp.secureserver.net92.204.80.0/24
92.204.80.19Mail server mailstore1.secureserver.net92.204.80.0/24

WHOIS of the domain iamp.us

Domain Name: iamp.us
Registry Domain ID: D46138338-US
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: whois.godaddy.com
Updated Date: 2025-08-04T18:00:56Z
Creation Date: 2014-07-30T14:35:48Z
Registry Expiry Date: 2027-07-29T23:59:59Z
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +1.4806242505
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited
Registry Registrant ID: C46149275-US
Registrant Name: Harbinder Khera
Registrant Organization:
Registrant Street: 2403 Sidney St, Ste 246
Registrant Street:
Registrant Street:
Registrant City: Pittsburgh
Registrant State/Province: PA
Registrant Postal Code: 15203
Registrant Country: us
Registrant Phone: +1.4122595843
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: [email protected]
Registrant Application Purpose: P1
Registrant Nexus Category: C21
Registry Admin ID: C46149277-US
Admin Name: Harbinder Khera
Admin Organization:
Admin Street: 2403 Sidney St, Ste 246
Admin Street:
Admin Street:
Admin City: Pittsburgh
Admin State/Province: PA
Admin Postal Code: 15203
Admin Country: us
Admin Phone: +1.4122595843
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: [email protected]
Admin Application Purpose: P1
Admin Nexus Category: C21
Registry Tech ID: C46149276-US
Tech Name: Harbinder Khera
Tech Organization:
Tech Street: 2403 Sidney St, Ste 246
Tech Street:
Tech Street:
Tech City: Pittsburgh
Tech State/Province: PA
Tech Postal Code: 15203
Tech Country: us
Tech Phone: +1.4122595843
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: [email protected]
Tech Application Purpose: P1
Tech Nexus Category: C21
Name Server: pdns05.domaincontrol.com
Name Server: pdns06.domaincontrol.com
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2026-10-01T06:47:17Z <<<

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

.US WHOIS Complaint Tool - http://www.whoiscomplaints.us
Advanced WHOIS Instructions - http://whois.us/help.html

Registry Services, LLC, the Registry Administrator for .US, has collected this information for the WHOIS database through a .US-Accredited Registrar. This information is provided to you for informational purposes only and is designed to assist persons in determining contents of a domain name registration record in the registry database. 

Registry Services, LLC makes this information available to you "as is" and does not guarantee its accuracy. By submitting a WHOIS query, you agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data: 

(1) to allow, enable, or otherwise support the transmission of mass unsolicited, commercial advertising or solicitations via direct mail, electronic mail, or by telephone; 
(2) in contravention of any applicable data and privacy protection laws; or 
(3) to enable high volume, automated, electronic processes that apply to the registry (or its systems). 

Compilation, repackaging, dissemination, or other use of the WHOIS database in its entirety, or of a substantial portion thereof, is not allowed without our prior written permission. 

We reserve the right to modify or change these conditions at any time without prior or subsequent notification of any kind. By executing this query, in any manner whatsoever, you agree to abide by these terms. NOTE: FAILURE TO LOCATE A RECORD IN THE WHOIS DATABASE IS NOT INDICATIVE OF THE AVAILABILITY OF A DOMAIN NAME. All domain names are subject to certain additional domain name registration rules. For details, please visit our site at www.whois.us.
Domain Name: IAMP.US
Registry Domain ID: D46138338-US
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: https://www.godaddy.com
Updated Date: 2025-07-30T18:00:56Z
Creation Date: 2014-07-30T14:35:48Z
Registrar Registration Expiration Date: 2027-07-29T23:59:59Z
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +1.4806242505
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Domain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Registrant State/Province: PA
Registrant Country: US
Registrant Email: https://www.godaddy.com/whois/results.aspx?domain=IAMP.US&action=contactDomainOwner
Tech Email: https://www.godaddy.com/whois/results.aspx?domain=IAMP.US&action=contactDomainOwner
Name Server: PDNS05.DOMAINCONTROL.COM
Name Server: PDNS06.DOMAINCONTROL.COM
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2026-10-01T06:47:17Z <<<
For more information on Whois status codes, please visit https://icann.org/epp

TERMS OF USE: The data contained in this registrar's Whois database, while believed by the
registrar to be reliable, is provided "as is" with no guarantee or warranties regarding its
accuracy. This information is provided for the sole purpose of assisting you in obtaining
information about domain name registration records. Any use of this data for any other purpose
is expressly forbidden without the prior written permission of this registrar. By submitting
an inquiry, you agree to these terms and limitations of warranty. In particular, you agree not
to use this data to allow, enable, or otherwise support the dissemination or collection of this
data, in part or in its entirety, for any purpose, such as transmission by e-mail, telephone,
postal mail, facsimile or other means of mass unsolicited, commercial advertising or solicitations
of any kind, including spam. You further agree not to use this data to enable high volume, automated
or robotic electronic processes designed to collect or compile this data for any purpose, including
mining this data for your own personal or commercial purposes. Failure to comply with these terms
may result in termination of access to the Whois database. These terms may be subject to modification
at any time without notice.

**NOTICE** This WHOIS server is being retired. Please use our RDAP service instead.

% Query time: 843 msec
% WHEN: Thu Oct 01 06:47:16 UTC 2026