IPv4 Addresses
memorgiftables.com. 300 IN A 104.21.37.151 memorgiftables.com. 300 IN A 172.67.209.187
IPv6 Addresses
memorgiftables.com. 300 IN AAAA 2606:4700:3031:0:0:0:6815:2597 memorgiftables.com. 300 IN AAAA 2606:4700:3037:0:0:0:AC43:D1BB
Name Servers
memorgiftables.com. 1200 IN NS rick.ns.cloudflare.com. memorgiftables.com. 1200 IN NS venus.ns.cloudflare.com.
Mail Servers
memorgiftables.com. 300 IN MX 10 mail.memorgiftables.com.
SOA Details
memorgiftables.com. 1200 IN SOA rick.ns.cloudflare.com. dns.cloudflare.com. 2402964453 10000 2400 604800 1800
Certificate Authority Authorization
No CAA records were returned at this registrable domain name. With no CAA policy, any public certificate authority (CA) may issue TLS certificates for names under this zone unless a parent publishes CAA; add issue / issuewild / iodef records to restrict issuance.
DMARC
Organizational policy (p): how receivers treat mail that fails aligned DMARC checks — none (monitor only), quarantine (often junk), or reject (block).
pct: share of mail that gets quarantine/reject; 100 = all failing messages (default).
100Aggregate DMARC reports (ZIP/XML). Optional but recommended for visibility.
Forensic (per-failure) reports. Often omitted for privacy or volume.
memorgiftables.com. 300 IN DMARC v=DMARC1; p=none;
DKIM
memorgiftables.com. 300 IN DKIM v=DKIM1; h=sha256; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEArBGGZMhrMQ2zFuWSKqJuagXiGS6AQSmsXjvOBSn8jW2fD7aQ5tfBFLA1oZ1lZzsv2e5DpkoArWfnSdisG37jSwBVvOyRow78LlPc3/7PYQbvPRaItcmU/sF++6K/lVSH3OKh7Ys9wf7R057AmvqL7ITKxjTbf3+jIZrgCvTRgjA2e2E4ue6ZCDBuVDQSTA0NPNnVoLOMHkIJKavvyqF1imgDtjOBgwWZBwts9hFW/5KpxpxxP1Zy6Wj7bSMovWJVjPYcyC3iVpB142JFIDE+FCHmRUMeAl25+R0TKZE3rpr3Z/qLYNo3980IQHGllTrpW6AAhf2Q0ZoRGfldGsDBYwIDAQAB
SPF (Sender Policy Framework)
| Qualifier | Mechanism | Target / value | Valid | Details |
|---|---|---|---|---|
| + Pass | a |
—
|
|
|
| + Pass | mx |
—
|
|
|
| + Pass | ip4 |
|
||
| ~ Softfail | all |
—
|
|
memorgiftables.com. 300 IN TXT "v=spf1 a mx ip4:136.243.154.119 ~all"
MTA-STS
This hostname does not publish an MTA-STS policy (no v=STSv1 TXT at _mta-sts.<name> and/or no policy at https://mta-sts.<name>/.well-known/mta-sts.txt).